git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org, "Jeff King" <peff@peff.net>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH 3-24/24] Documentation: include configuration options in manpages
Date: Mon, 26 Jul 2010 14:55:52 -0500	[thread overview]
Message-ID: <20100726195552.GA1451@burratino> (raw)
In-Reply-To: <a0be121e0b89f010273f3a3de9ad054bcec26d6c.1280169048.git.trast@student.ethz.ch>

Thomas Rast wrote:

> +++ 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. :)

[...]
> +++ 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?

[...]
> +++ 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

  reply	other threads:[~2010-07-26 20:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 18:48 [RFC PATCH 0/24] Documentation: refactor config variable descriptions Thomas Rast
2010-07-26 18:48 ` [PATCH 2/24] Documentation: Add variable-substitution script Thomas Rast
2010-07-26 19:51   ` Jonathan Nieder
2010-07-26 20:27     ` Ævar Arnfjörð Bjarmason
2010-07-26 21:17   ` Jakub Narebski
2010-07-26 21:49     ` Ævar Arnfjörð Bjarmason
2010-07-26 18:48 ` [PATCH 3-24/24] Documentation: include configuration options in manpages Thomas Rast
2010-07-26 19:55   ` Jonathan Nieder [this message]
2010-07-26 19:05 ` [RFC PATCH 0/24] Documentation: refactor config variable descriptions Ævar Arnfjörð Bjarmason
     [not found] ` <75c9db91f5ab43ebb60cace0d20389462a2ab02c.1280169048.git.trast@student.ethz.ch>
2010-07-26 19:38   ` [PATCH 1/24] Documentation: Move variables from config.txt to separate file Jonathan Nieder
2010-07-26 20:18     ` Ævar Arnfjörð Bjarmason
2010-07-27  6:48       ` Sverre Rabbelier
2010-07-28 17:23       ` Junio C Hamano
2010-07-26 22:25 ` [RFC PATCH 0/24] Documentation: refactor config variable descriptions Ævar Arnfjörð Bjarmason

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100726195552.GA1451@burratino \
    --to=jrnieder@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=trast@student.ethz.ch \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).