On Wednesday 17 October 2007 20:54, Linus Torvalds wrote: > On Wed, 17 Oct 2007, Tom Tobin wrote: > > Or is "unix developers" code for "my sample size of one"? > > Well, let's put it this way: that "sample" is the one that started the > project. > > I got to pick the license. Are you going to argue about that too? I got to > pick the way I wrote the code. Are you going to continue arguing about > that? > > The fact is, I don't see the people arguing for spaces having actually > *done* anything for git. So why are you arguing? Possibly because they do not want to cooperate :-) Anyway, it is mostly a Unix <-> the rest issue. In the Unix world all tools by default use 8-spaces per tab and although most of them can be told otherwise, nobody bothers. That way at least all code looks the same, regardless of spaces or tabs. Many editors are smart enough to create sequences N<TAB>+M<SPACE> for initial indentation to get consistent usage, but even if it isn't consistent patch and diff can be told to handle it. Outside the Unix world there appears to be little standard, so you receive files with any combination of tab distance, using tabs vs. spaces, etc. Most often I have to re-indent them before reading :-( I guess the most ideal situation is to use only tabs for initial indentation and spaces elsewhere, so changing the tab distance gets consistent layout. The drawback is that there is no room for `half indentation', so style conventions have to take care of that. Still, the main developers take the decision. If you don't like it, don't cooperate or fork. --- Jan - 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
