Ramkumar Ramachandra <artag...@gmail.com> writes:
> Junio C Hamano wrote:
>> With a weaker phrase, e.g. "These configuration variables may be of
>> interest", such a list may not hurt readers, but personally I do not
>> think it adds much value to have a list of variables without even a
>> single line description of what each is used for.
> Okay. Does this work?
Hrm, is it useful without even a single line description of what
each is used for?
Besides, how does it appear in the formatted documents? A thick
paragraph that lists names of variables enumerated without comma in
> -- 8< --
> From: Ramkumar Ramachandra <artag...@gmail.com>
> Date: Sun, 7 Oct 2012 17:24:36 +0530
> Subject: [PATCH] Documentation/git-push: add a configuration variables
> The list of configuration variables that affect the operation of a git
> command can often be hard to find. As a first step, add a
> "Configuration variables" section to git-push. The intent is to
> create similar sections in all manpages.
> Signed-off-by: Ramkumar Ramachandra <artag...@gmail.com>
> Documentation/git-push.txt | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
> index cb97cc1..a125536 100644
> --- a/Documentation/git-push.txt
> +++ b/Documentation/git-push.txt
> @@ -426,6 +426,30 @@ Commits A and B would no longer belong to a
> branch with a sy
> and so would be unreachable. As such, these commits would be removed by
> a `git gc` command on the origin repository.
> +Configuration variables
> +These configuration variables may be of interest. For more
> +information see linkgit:git-config.
> Part of the linkgit:git suite
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html