{"thread":{"id":"4423","subject":"[PATCH] Document git aliases support","startedAt":"2006-06-07T18:43:50Z","lastAt":"2006-06-07T20:11:34Z","messageCount":3,"participants":["Petr Baudis","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"21392","messageId":"20060607184350.31338.46653.stgit@machine.or.cz","threadId":"4423","inReplyTo":null,"subject":"[PATCH] Document git aliases support","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2006-06-07T18:43:50Z","receivedAt":"2006-06-07T18:43:50Z","isPatch":true,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"This patch ports and modifies appropriately the git aliases documentation\nfrom my patch, shall it rest in peace.\n\nSigned-off-by: Petr Baudis \n---\n\n Documentation/config.txt | 7 +++++++\n Documentation/git.txt | 3 +++\n 2 files changed, 10 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex c861c6c..ad9ec3e 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -91,6 +91,13 @@ core.warnAmbiguousRefs::\n \tIf true, git will warn you if the ref name you passed it is ambiguous\n \tand might match multiple refs in the .git/refs/ tree. True by default.\n \n+alias.*::\n+\tCommand aliases for the gitlink:git[1] command wrapper - e.g.\n+\tafter defining \"alias.last = cat-file commit HEAD\", the invocation\n+\t\"git last\" is equivalent to \"git cat-file commit HEAD\". You cannot\n+\toverride even existing command names with aliases. Arguments are\n+\tsplit by spaces, the usual shell quoting and escaping is supported.\n+\n apply.whitespace::\n \tTells `git-apply` how to handle whitespaces, in the same way\n \tas the '--whitespace' option. See gitlink:git-apply[1].\ndiff --git a/Documentation/git.txt b/Documentation/git.txt\nindex 24ca55d..e474bdf 100644\n--- a/Documentation/git.txt\n+++ b/Documentation/git.txt\n@@ -21,6 +21,9 @@ link:everyday.html[Everyday Git] for a u\n \"man git-commandname\" for documentation of each command. CVS users may\n also want to read link:cvs-migration.html[CVS migration].\n \n+The COMMAND is either a name of a Git command (see below) or an alias\n+as defined in the configuration file (see gitlink:git-repo-config[1]).\n+\n OPTIONS\n -------\n --version::\n"},{"id":"21395","messageId":"7vzmgog5ce.fsf@assigned-by-dhcp.cox.net","threadId":"4423","inReplyTo":"20060607184350.31338.46653.stgit@machine.or.cz","subject":"Re: [PATCH] Document git aliases support","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-06-07T18:58:57Z","receivedAt":"2006-06-07T18:58:57Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Petr Baudis writes:\n\n> Documentation/config.txt | 7 +++++++\n> Documentation/git.txt | 3 +++\n> 2 files changed, 10 insertions(+), 0 deletions(-)\n\nThanks.\n\n> diff --git a/Documentation/config.txt b/Documentation/config.txt\n> index c861c6c..ad9ec3e 100644\n> --- a/Documentation/config.txt\n> +++ b/Documentation/config.txt\n> @@ -91,6 +91,13 @@ core.warnAmbiguousRefs::\n> \tIf true, git will warn you if the ref name you passed it is ambiguous\n> \tand might match multiple refs in the .git/refs/ tree. True by default.\n> \n> +alias.*::\n> +\tCommand aliases for the gitlink:git[1] command wrapper - e.g.\n> +\tafter defining \"alias.last = cat-file commit HEAD\", the invocation\n> +\t\"git last\" is equivalent to \"git cat-file commit HEAD\". You cannot\n> +\toverride even existing command names with aliases. Arguments are\n> +\tsplit by spaces, the usual shell quoting and escaping is supported.\n> +\n\n\"even\"? How about: \"alias that hides existing command names are\nnot used to avoid confusion\"?\n"},{"id":"21398","messageId":"20060607201134.GC2609@pasky.or.cz","threadId":"4423","inReplyTo":"7vzmgog5ce.fsf@assigned-by-dhcp.cox.net","subject":"[PATCH] Document git aliases support","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2006-06-07T20:11:34Z","receivedAt":"2006-06-07T20:11:34Z","isPatch":true,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Wed, Jun 07, 2006 at 08:58:57PM CEST, I got a letter\nwhere Junio C Hamano said that...\n> Petr Baudis writes:\n> > diff --git a/Documentation/config.txt b/Documentation/config.txt\n> > index c861c6c..ad9ec3e 100644\n> > --- a/Documentation/config.txt\n> > +++ b/Documentation/config.txt\n> > @@ -91,6 +91,13 @@ core.warnAmbiguousRefs::\n> > \tIf true, git will warn you if the ref name you passed it is ambiguous\n> > \tand might match multiple refs in the .git/refs/ tree. True by default.\n> > \n> > +alias.*::\n> > +\tCommand aliases for the gitlink:git[1] command wrapper - e.g.\n> > +\tafter defining \"alias.last = cat-file commit HEAD\", the invocation\n> > +\t\"git last\" is equivalent to \"git cat-file commit HEAD\". You cannot\n> > +\toverride even existing command names with aliases. Arguments are\n> > +\tsplit by spaces, the usual shell quoting and escaping is supported.\n> > +\n> \n> \"even\"? How about: \"alias that hides existing command names are\n> not used to avoid confusion\"?\n\nOops, that \"even\" was not meant to be there. I have rephrased it a bit.\n\n---\n\nThis patch ports and modifies appropriately the git aliases documentation\nfrom my patch, shall it rest in peace.\n\nSigned-off-by: Petr Baudis \n---\n\n Documentation/config.txt | 8 ++++++++\n Documentation/git.txt | 3 +++\n 2 files changed, 11 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex c861c6c..91615c1 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -91,6 +91,14 @@ core.warnAmbiguousRefs::\n \tIf true, git will warn you if the ref name you passed it is ambiguous\n \tand might match multiple refs in the .git/refs/ tree. True by default.\n \n+alias.*::\n+\tCommand aliases for the gitlink:git[1] command wrapper - e.g.\n+\tafter defining \"alias.last = cat-file commit HEAD\", the invocation\n+\t\"git last\" is equivalent to \"git cat-file commit HEAD\". It is not\n+\tallowed to redefine existing command names using aliases to avoid\n+\tconfusion and troubles with script usage. Arguments are split by\n+\tspaces, the usual shell quoting and escaping is supported.\n+\n apply.whitespace::\n \tTells `git-apply` how to handle whitespaces, in the same way\n \tas the '--whitespace' option. See gitlink:git-apply[1].\ndiff --git a/Documentation/git.txt b/Documentation/git.txt\nindex 24ca55d..e474bdf 100644\n--- a/Documentation/git.txt\n+++ b/Documentation/git.txt\n@@ -21,6 +21,9 @@ link:everyday.html[Everyday Git] for a u\n \"man git-commandname\" for documentation of each command. CVS users may\n also want to read link:cvs-migration.html[CVS migration].\n \n+The COMMAND is either a name of a Git command (see below) or an alias\n+as defined in the configuration file (see gitlink:git-repo-config[1]).\n+\n OPTIONS\n -------\n --version::\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nA person is just about as big as the things that make them angry.\n"}]}