git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
	Ramkumar Ramachandra <artagnon@gmail.com>,
	David Glasser <glasser@davidglasser.net>,
	git@vger.kernel.org
Subject: Re: push.default documented in "man git-push"?
Date: Wed, 3 Oct 2012 17:40:51 -0400	[thread overview]
Message-ID: <20121003214051.GD4484@sigill.intra.peff.net> (raw)
In-Reply-To: <7v7gr75s40.fsf@alter.siamese.dyndns.org>

On Wed, Oct 03, 2012 at 11:26:55AM -0700, Junio C Hamano wrote:

> Please do not label the list as "These variables affect this
> command" to give a false impression that it is the complete list if
> it isn't.
> 
> Unless somebody promises to keep an up-to-date complete list there
> (or even better, come up with a mechanism to help us keep that
> promise automatically, perhaps by annotating pieces with structured
> comments in config.txt and automatically appending such a section to
> manual pages of relevant commands), that is.
>
> 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.

We talked a while ago about actually moving the config options into the
individual manpages, and generating config.txt to simply contain an
index of keys and where their definitions may be found. That also has
the "list without description" characteristic. But presumably you would
be looking for keys in the manual of the command you want to affect, and
the master list would mostly be for redirecting you to the right
manpage.

It does break down a little when you have keys that could go in multiple
pages. In many cases, this can be solved by a canonical location that
describes the shared concepts. For example, `diff.*` should probably go
into a `gitdiff(7)` that talks about the various diff options and
formats.

Of course, that only works if you think pulling out the shared diff bits
from git-diff*, git-log, etc into a separate manpage is a good idea. I
do, because I think it makes it more clear to the reader how the
concepts connect (as opposed to simply including shared bits inline in
the manpages, as we do now, with no indication that the same content is
going to apply in many places). But it does have a downside that
individual manpages are not as easily searchable via the pager, as you
may have to follow a cross-reference to find what you want.

-Peff

  reply	other threads:[~2012-10-04 21:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02  0:25 push.default documented in "man git-push"? David Glasser
2012-10-02 15:09 ` Ramkumar Ramachandra
2012-10-02 15:18   ` David Glasser
2012-10-02 15:38     ` Ramkumar Ramachandra
2012-10-02 16:45       ` Matthieu Moy
2012-10-02 16:56         ` Ramkumar Ramachandra
2012-10-02 17:21         ` Junio C Hamano
2012-10-02 17:25           ` Matthieu Moy
2012-10-02 18:34       ` Junio C Hamano
2012-10-02 19:00         ` David Glasser
2012-10-02 19:08           ` Junio C Hamano
2012-10-03  7:54         ` Matthieu Moy
2012-10-03  8:52         ` Ramkumar Ramachandra
2012-10-03  8:14   ` Nguyen Thai Ngoc Duy
2012-10-03  8:17     ` Ramkumar Ramachandra
2012-10-03  8:23       ` Nguyen Thai Ngoc Duy
2012-10-03  8:46         ` Ramkumar Ramachandra
2012-10-03 10:18           ` Nguyen Thai Ngoc Duy
2012-10-03 18:26             ` Junio C Hamano
2012-10-03 21:40               ` Jeff King [this message]
2012-10-08 17:12                 ` Junio C Hamano
2012-10-07 16:09               ` Ramkumar Ramachandra
2012-10-07 20:27                 ` Junio C Hamano
2012-10-08  7:27                   ` Ramkumar Ramachandra
2012-10-08  8:35                     ` Nguyen Thai Ngoc Duy
2012-10-03 18:49             ` Junio C Hamano
2012-10-04  2:01               ` Nguyen Thai Ngoc Duy
2012-10-04  5:45                 ` Junio C Hamano
2012-10-05  6:34                   ` Nguyen Thai Ngoc Duy
2012-10-05 20:03                     ` Junio C Hamano
2012-10-11 12:43                       ` Nguyen Thai Ngoc Duy
2012-10-11 14:18                         ` Matthieu Moy
2012-10-11 14:43                           ` Nguyen Thai Ngoc Duy
2012-10-11 16:17                           ` Junio C Hamano
2012-10-03 11:58     ` Peter Krefting

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=20121003214051.GD4484@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=glasser@davidglasser.net \
    --cc=pclouds@gmail.com \
    /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).