From: Junio C Hamano <gitster@pobox.com>
To: Namhyung Kim <namhyung.kim@lge.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/3] help: Add '--follow-alias' option
Date: Wed, 14 Mar 2012 23:00:26 -0700 [thread overview]
Message-ID: <7vehsummit.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1331779969-8641-2-git-send-email-namhyung.kim@lge.com> (Namhyung Kim's message of "Thu, 15 Mar 2012 11:52:48 +0900")
Namhyung Kim <namhyung.kim@lge.com> writes:
> The --follow-alias option will look up the alias definitions and
> use the first word as a command. For example, if I set my aliases
> as follows:
>
> $ git help br
> `git br' is aliased to `git branch'
> $ git help ru
> `git ru' is aliased to `git remote update'
>
> adding --follow-alias (or -f) option will show man pages of
> git-branch and git-remote, respectively.
What would happen when somebody has this?
[alias]
br = branch --list
$ git help --follow-alias br
... man page for git-branch is shown ...
NAK.
> +-f::
> +--follow-alias::
> + Read alias definitions and use its first word as a command name
> + (if any).
Also, please do not let a potentially ill-conceived option to squat on a
short and sweet single letter option name, until it proves to be useful.
next prev parent reply other threads:[~2012-03-15 6:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 2:52 [PATCH 1/3] help: Fix help message for aliases Namhyung Kim
2012-03-15 2:52 ` [PATCH 2/3] help: Add '--follow-alias' option Namhyung Kim
2012-03-15 6:00 ` Junio C Hamano [this message]
2012-03-15 6:15 ` 김남형
2012-03-15 6:23 ` Junio C Hamano
2012-03-15 6:46 ` Namhyung Kim
2012-03-15 7:09 ` Junio C Hamano
2012-03-15 2:52 ` [PATCH 3/3] help: Add 'help.follow-alias' config item Namhyung Kim
2012-03-15 6:06 ` Junio C Hamano
2012-03-15 6:29 ` Namhyung Kim
2012-03-15 4:17 ` [PATCH 1/3] help: Fix help message for aliases Jeff King
2012-03-15 5:15 ` 김남형
2012-03-15 13:19 ` Jeff King
2012-03-15 5:23 ` Junio C Hamano
2012-03-15 5:48 ` 김남형
2012-03-15 6:18 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vehsummit.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=namhyung.kim@lge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.