The core.autocrlf serting is local. There is no way to propagate it
from upstream repo to downstream repo. This leads to confusion and
dirty commits in every git project i have worked with, and i have made
this mistake more than once.
It sounds good to have LF in the repo, and whatever the platform dev
desires in the working tree. That is true in win and input or false on
*nix. Haven't worked with mono, but using true on win have worked
great so far for me. Btw spark and fluentnh both are using false and
therefore has CRLF in repos, have anybody heard about problems
with that?
Sent from my iPhone
On 30/03/2010, at 09.31, Julian Birch <[email protected]> wrote:
Sorry, the unix setting is "input"
On Tuesday, March 30, 2010, Julian Birch <[email protected]>
wrote:
James Foster on the dotless project believes he has a solution. But
it requires co-ordination of everyone involved. I think the CRLF
setting has to be set to true on windows and auto on unix/mac.
J
On Tuesday, March 30, 2010, Krzysztof Koźmic (2) <krzysz...@kozmic
.pl> wrote:
I'm starting a new thread for this, not to pollute the other
discussion.
I vote *for* frictionless working with Git. As discussed before I
had
issues with files shown as modified just after I did clean clone. I
have this working now, but while fixing one thing, that introduced
another.
In repository we keep files with lf, and I work on Windows. When I
add
a new file it gets added with crlf which leads to us having mixed
lines ending in the repository.
Worse, when I start editing lf file, it breaks ReSharper, which
can't
handle them. Every refactoring either blows up my VS or ends up with
me having a file with mixed line endings. I then tell VS to convert
line endings to crlf so that I can work with it and with ReSharper,
and then change line endings back manually in Notepad++.
Hopefully I don't have to tell you what PITA that is.
So I'm for resolving these issues, by whatever means people more
experienced with Git than myself find best.
Krzysztof
On 30 Mar, 03:26, Mauricio Scheffer <[email protected]>
wrote:
Yes, it can be changed at any time (not for the entire history of
course,
that would need history rewriting), it's not hard, seehttp://
help.github.com/dealing-with-lineendings/
<http://help.github.com/dealing-with-lineendings/>This was
discussed not
long ago and several people voted against autocrlf so it remains
that way:http://www.mail-archive.com/[email protected]
/msg...
<http://www.mail-archive.com/[email protected]/msg
...>
Cheers,
Mauricio
--
You received this message because you are subscribed to the Google
Groups "Castle Project Development List" group.
To post to this group, send email to [email protected]
.
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
.
--
You received this message because you are subscribed to the Google
Groups "Castle Project Development List" group.
To post to this group, send email to [email protected]
.
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
.
--
You received this message because you are subscribed to the Google Groups "Castle
Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
