On Tue, 16 Oct 2007, Tom Tobin wrote:I do indeed. I don't think it's sensible. And I did think I already answered that issue by talking about how most editors don't even support it or show the difference between tabs and spaces. For example, the editor I use - microemacs - supports tabs just fine. It does auto-indentation etc. But it does it with hard-tabs by default, so now you have to have some editor-specific setup for that particular project if you ever want to do anything else. And that's really what it boils down to. Everybody support 8-character hardtabs (and usually by default). They may support other things *too*, but any time you move away from that standard behaviour, you'll most likely find something that doesn't support the alternatives. So yes, the answer really is: "git uses 8-character hard-tabs, live with it". Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg Kroah-Hartman | [PATCH 006/196] Chinese: add translation of oops-tracing.txt |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
| Borislav Petkov | 2.6.23-rc1: no setup signature found... |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [BUG] New Kernel Bugs |
