Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes: > On Fri, 11 Jan 2008, Steffen Prohaska wrote: >> >> Ah sorry, I misunderstood you in [1]. I thought your last point >> "Mixed Windows usage" meant what I have in mind: A user working >> in a mixed Windows/Unix environment who creates a file using >> Windows tools and commits it in the Unix environment. In this >> case the CRLF file will be transferred from Windows to Unix >> without git being involved. The right thing for git on Unix is >> to remove CRLF during a commit but still write only LF during >> check out. So autocrlf=input is the right choice. > > Oh, ok, I didn't realize. > > But yes, if you use a network share across windows and Unixand actually > *share* the working tree over it, then yes, you'd want "autocrlf=input" on > the unix side. > > However, I think that falls under the "0.1%" case, not the "99.9%" case. > > I realize that people probably do that more often with centralized > systems, but with a distributed thing, it probably makes a *ton* more > sense to have separate trees. But I could kind of see having a shared > development directory and accessing it from different types of machines > too. One case is when you only want to commit compiling code, and to test-compile on all platforms that you are supposed to be portable to you need to access the source tree on different systems before committing anything. You could of course commit optimistically and checkout on the other system, and then go back and rewrite the commits if you need to fix something. But that is a lot more work. -- David Kågedal - 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
