Hi
Checking on the autocrlf option, most of whose documentation just
says it makes it work 'right'.
autocrlf=true is what I particularly dislike.
I have no objection to autoconversion from Windows to Unix on input,
but it also does autoconversion in the reverse direction maximizing
the number of erroneous files in existence.
autocrlf=input looks much more promising
It only converts Windows to Unix, no reverse conversion. But does it
work? Does EGIT staging detect that no commit is needed for both
Windows and Unix line endings? Does Platform compare successfully
show no change? Does EMF Compare work sensibly? I doubt it. Why
would platform compare / EMF compare look at a repo-specific GIT
option?
How do you guarantee that all users always have consistent
non-standard EGIT settings?
I generally check files before committing, since I know that
EMF genmodel needs import repair, @Override repair
Xtext generate needs import repair, @Override repair, line endings
repair
....
Until repaired, commit lists are ridiculously large.
Regards
Ed
On 20/02/2015 00:25, Adolfo
Sánchez-Barbudo Herrera wrote:
Hi Ed,
I think you are missing the point of the current need of
being careful to not commit windows line endings, which can
be/are currently produced in windows environments by tools
such as the widespread EMF. It´s very easy to forget to pass
that specific option when saving.
I think I don´t have anything else to contribute to this
discussion. Let it be as it is. At least now a "better"
saving is done in the cs2as.tests test cases.
Regards,
Adolfo.
_______________________________________________
qvtd-dev mailing list
qvtd-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/qvtd-dev
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5646 / Virus Database: 4284/9146 - Release Date:
02/19/15
|