Miles Bader <miles@xxxxxxx> writes: > Junio C Hamano <gitster@xxxxxxxxx> writes: > > > > git branch --help > > > > > > How about "git help branch"? > > > > The reason why we do not do what you seem to be suggesting is because > > giving the same behaviour to "git b --help" as "git branch --help" is > > wrong. > > I agree with Gelonida's followup: although what you say makes sense, > it's still pretty annoying behavior for the very common case of a > simple renaming alias... > > E.g., I have "co" aliased to "checkout", and so my fingers are very > very inclined to say "co" when I mean checkout... including when > asking for help. I actually end up typing "git co --help", grumbling, > and retyping with the full command name, quite reguarly. > > What I've often wished is that git's help system would output > something like: > > $ git help co > `git co' is aliased to `checkout' > > Here's the help entry for `checkout': > > GIT-CHECKOUT(1) Git Manual GIT-CHECKOUT(1) Wouldn't it be more useful to say something like this: $ git co --help `git co' is aliased to `checkout' You can see help entry for `checkout' with "git checkout --help" Then help is only copy'n'paste away. (This helping text probably should be controlled by some advice.* config variable). P.S. I wonder if allowing to run command if you specify unambiguous prefix would be a good replacement for such aliases? -- Jakub Narębski -- 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