On Tue, 8 Jan 2008 13:31:57 -0800 (PST) Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > So the only thing you'd need to add is to add a > > /* No naked LF's! */ > if (safecrlf && stats.lf) > return 0; > > to that sequence too, but the thing is, having mixed line-endings isn't > actually all that unusual, so I think that kind of "autocrlf=safe" thing > is actually almost useless - because when that thing triggers, you almost > always *do* want to convert it to be just one way. > > I've seen it multiple times when people cooperate with windows files with > unix tools, where unix editors often preserve old CRLF's, but write new > lines with just LF. > > So "autocrlf=safe" would be trivial to add, but I suspect it would cause > more confusion than it would fix. But isn't the entire point of this exercise to ensure that you will never be in the situation on Linux where you checkout files that have CRLF endings? And conversely that on Windows you will never checkout files that have LF endings? If so, you don't have to worry about your tools creating mixed ending files. The only time the above rules should be broken, is when the user explicitly states that their tools will do-the-right-thing without such help. Sean - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
