|Re: More line ending problems [message #1247899 is a reply to message #1241532]
||Sun, 16 February 2014 14:09
| Robin Rosenberg
Registered: July 2009
Eike Stepper skrev 2014-02-08 05.14:|
> Am 07.02.2014 21:44, schrieb Matthias Sohn:
>> - Which EGit version are you using ?
> That's EGit 126.96.36.199402060118
>> - which autocrlf options are you using ?
> core.autocrlf = true
> core.filemode = false
>> - could you retry using a current nightly build version, there was a patch fixing some autocrlf problem
>> which was submitted on Feb 2: https://git.eclipse.org/r/#/c/20173/
> I think my nightly is already newer and should contain that patch. Is a new clone required?
> BTW. I found out that even CGit reports these 3800 dirty files (at least 3500 of them not really changed). No idea if that's a follow-up effect of EGit dealing with the
> dirty states first.
How does it report that? git status/git diff checks status by reading files when necessary, while e.g. gitk only checks the index and may report changed files without.
changes after using EGit.
You can try setting core.checkstat to minimal to avoid that. That makes C Git only check the file stat fields that JGit knows about.
> Another bad effect is that Eclipse in general becomes very sluggish when so many files are dirty (i.e., listed in the staging view), sometimes to the extent that I have to
> kill it because it's totally frozen.
That sluggishness is probably because we do not update the index after figuring out the dirtyness (unlike C Git). There's an issue for that.
Powered by FUDForum
. Page generated in 0.02066 seconds