|Re: [jgit-dev] Quick question about WorkingTreeIterator::contentCheck|
that rings a bell. Could it be that you have files which paths differ only in case. Like 'd/f' and 'd/F'. That works well on case sensitive filesystems (often on linux) but when checking out on windows (but also on MacOS) that causes problems. Writing the two files d/f and d/F will not create two different files. Check with 'git ls-files' whether you have such a case.
Von: jgit-dev-bounces@xxxxxxxxxxx <jgit-dev-bounces@xxxxxxxxxxx> im Auftrag von Peter Hull <peterhull90@xxxxxxxxx>
Gesendet: Mittwoch, 11. März 2020 09:28
An: JGit Developers list <jgit-dev@xxxxxxxxxxx>
Betreff: Re: [jgit-dev] Quick question about WorkingTreeIterator::contentCheck
On Tue, 10 Mar 2020 at 22:01, Thomas Wolf <thomas.wolf@xxxxxxxxxx> wrote:
> On 10 Mar 2020, at 18:39 , Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:
> > this should not happen, JGit first compares file meta data to detect modification (since that's faster),
> > if this fails it compares the actual file content by comparing objectIDs (hash over the object's content).
> > I guess you meant WorkingTreeIterator#isModified
I did, sorry for the confusion.
> Which JGit version?
In a checkout of NB's git I have two copies of
org.eclipse.jgit-126.96.36.199501210735-r.jar (with different sizes) and
one of org.eclipse.jgit-188.8.131.52909110433-r.jar! However in the
combined binary there is just
org-eclipse-jgit.jar and it is identical to the 5.5.0 version.
I assume that replacing 5.5.0 -> 5.5.1 would not require any changes
to the calling code?
However, this should be a performance change shouldn't it, files
should still be marked correctly even if jgit has to go through the
slower route of checking file contents?
> Otherwise, perhaps it's line endings. Check that the files do not use mixed line endings,
> and double-check your autoCrlf and other git config settings and .gitattributes related
> to line endings.
I'll check this, because I did the original clones from 'git for
Windows' (git bash) and then saw the spurious changes in Netbeans
Also I tried the same on MacOS and it worked perfectly.
I will report back if I figure it out; in the meantime thanks again
for your patience, there's quite a lot of new information to digest
jgit-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jgit-dev
Back to the top