Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EGit » More line ending problems
More line ending problems [message #1241276] Fri, 07 February 2014 18:48 Go to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 5590
Registered: July 2009
Senior Member
Hi,

When I generate JavaDocs I end up with 3800 dirty files in my workspace. For some reason JavaDoc decides to generate
some lines with LF and some with CRLF (I'm on Windows). I fix that with an Ant script:

<fixcrlf srcdir="plugins\my.plugin" includes="**/*.html" />

After that the files are still dirty although no change is shown when I open the Compare editor on one of them. How's
that possible? What am I doing wrong?

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Re: More line ending problems [message #1241335 is a reply to message #1241276] Fri, 07 February 2014 20:44 Go to previous messageGo to next message
Matthias Sohn is currently offline Matthias SohnFriend
Messages: 612
Registered: July 2009
Senior Member
- Which EGit version are you using ?
- which autocrlf options are you using ?
- 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/
Re: More line ending problems [message #1241532 is a reply to message #1241335] Sat, 08 February 2014 04:14 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 5590
Registered: July 2009
Senior Member
Am 07.02.2014 21:44, schrieb Matthias Sohn:
> - Which EGit version are you using ?
That's EGit 3.3.0.201402060118

> - 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.

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.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Re: More line ending problems [message #1247899 is a reply to message #1241532] Sun, 16 February 2014 19:09 Go to previous message
Robin Rosenberg is currently offline Robin RosenbergFriend
Messages: 332
Registered: July 2009
Senior Member
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 3.3.0.201402060118
>
>> - 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.

-- robin
Previous Topic:Egit and submodules [RESOLVED]
Next Topic:Sub module DIRTY-IN-WORKTREE problem when merging
Goto Forum:
  


Current Time: Sun Dec 21 22:31:42 GMT 2014

Powered by FUDForum. Page generated in 0.01619 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software