From: Junio C Hamano <junkio@cox.net>
Date: Wed, 07 Jun 2006 18:58:57 GMT
Subject: Re: [PATCH] Document git aliases support
Message-ID: <7vzmgog5ce.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20060607184350.31338.46653.stgit@machine.or.cz>

Petr Baudis <pasky@suse.cz> writes:

>  Documentation/config.txt |    7 +++++++
>  Documentation/git.txt    |    3 +++
>  2 files changed, 10 insertions(+), 0 deletions(-)

Thanks.

> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index c861c6c..ad9ec3e 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -91,6 +91,13 @@ core.warnAmbiguousRefs::
>  	If true, git will warn you if the ref name you passed it is ambiguous
>  	and might match multiple refs in the .git/refs/ tree. True by default.
>  
> +alias.*::
> +	Command aliases for the gitlink:git[1] command wrapper - e.g.
> +	after defining "alias.last = cat-file commit HEAD", the invocation
> +	"git last" is equivalent to "git cat-file commit HEAD". You cannot
> +	override even existing command names with aliases. Arguments are
> +	split by spaces, the usual shell quoting and escaping is supported.
> +

"even"?  How about: "alias that hides existing command names are
not used to avoid confusion"?