Re: [PATCH 3-24/24] Documentation: include configuration options in manpages

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Jul 26, 2010, 19:55 UTC
Message-ID: <20100726195552.GA1451@burratino>
In-Reply-To: <a0be121e0b89f010273f3a3de9ad054bcec26d6c.1280169048.git.trast@student.ethz.ch>

Thomas Rast wrote:

Show 11 quoted lines

> +++ b/Documentation/git-add.txt
> @@ -148,10 +148,8 @@ subdirectories.
>  Configuration
>  -------------
>  
> -The optional configuration variable `core.excludesfile` indicates a path to a
> -file containing patterns of file names to exclude from git-add, similar to
> -$GIT_DIR/info/exclude.  Patterns in the exclude file are used in addition to
> -those in info/exclude.  See linkgit:gitrepository-layout[5].
> +@@CONFIG(add.ignore-errors)@@
> +@@CONFIG(core.excludesfile)@@

Hmm, the packrat in me does not like cavalierly throwing away text like this. :)

[...]

Show 13 quoted lines

> +++ b/Documentation/git-archive.txt
> @@ -93,12 +93,8 @@ zip
>  CONFIGURATION
>  -------------
>  
> -tar.umask::
> -	This variable can be used to restrict the permission bits of
> -	tar archive entries.  The default is 0002, which turns off the
> -	world write bit.  The special value "user" indicates that the
> -	archiving user's umask will be used instead.  See umask(2) for
> -	details.
> +@@CONFIG(tar.umask)@@
> +

Can this genre of change be automated?

[...]

Show 12 quoted lines

> +++ b/Documentation/git-branch.txt
> @@ -222,6 +222,14 @@ but different purposes:
>  - `--no-merged` is used to find branches which are candidates for merging
>    into HEAD, since those branches are not fully contained by HEAD.
>  
> +
> +CONFIGURATION
> +-------------
> +
> +@@CONFIG(branch.autosetupmerge)@@
> +@@CONFIG(branch.autosetuprebase)@@
> +

Obviously a good thing.

Thanks. Jonathan