well this is just the "normal" challenges with git and file endings explained
here, does not explain why egit is behaving different from command line git ?
On 09 Jan 2013, at 14:46, Fred Bricon <fbricon(a)redhat.com> wrote:
So it seems this is a kind of known issue :
http://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg09216.html
Le 09/01/2013 13:57, Fred Bricon a écrit :
> Hi, I never use egit usually, as I always had bad surprises in the past,
> I mostly prefer CLI.
> Today I decided to give it a new chance so I committed and pushed a few
> files using the awesome git staging view.
>
> And then I opened
>
https://github.com/jbosstools/jbosstools-central/commit/aa0efbc9d811fb467...
>
> All lines are shown as changed (line endings crap I assume). How
> awesome...not is that?
>
> I'm on windows with core.autocrlf=true, in egit, 'ignore whitespace
> changes' is UNCHECKED, so I have no idea of what happened.
>
> So, if you haven't used egit (on windows) yet, well, be careful then.
>
> Angry Fred
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev