On Tue, Aug 26, 2008 at 06:04:00PM +0200, Matthias Kestenholz wrote: > Correct, but there is a benefit. Imagine a new user: > > git-<tab><tab> ... what? 140-something commands? I'll better start looking > for alternatives _right now_! Actually, this is the only realistic argument I can remember at all. Are there any others? I couldn't come up with any - but I didn't do much history digging: others seem to be equally in dark, though. (And I'm not saying this one is not important; it's apparently a significant "P.R." issue. But is just this _the_ official rationale?) > Having a cluttered namespace is never a good thing. It means that it's > less obvious which commands you are supposed to use etc. This is not much of a valid argument; you could install the same set of commands to /usr/bin that you are offering in the bash autocompletion. (With the catch that this might break peoples scripts in a subtler way than just removing all of them.) -- Petr "Pasky" Baudis The next generation of interesting software will be done on the Macintosh, not the IBM PC. -- Bill Gates -- 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
