From: Jakub Narebski <jnareb@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Jari Aalto <jari.aalto@cante.net>,
Thomas Rast <trast@student.ethz.ch>,
git@vger.kernel.org
Subject: Re: [PATCH] Documentation/config.txt: Order variables alphabetically
Date: Thu, 2 Dec 2010 00:38:52 +0100 [thread overview]
Message-ID: <201012020038.55019.jnareb@gmail.com> (raw)
In-Reply-To: <20101201180332.GC7774@sigill.intra.peff.net>
On Wed, 1 Dec 2010, Jeff King wrote:
> On Wed, Dec 01, 2010 at 07:10:55PM +0200, Jari Aalto wrote:
>
> > 2010-12-01 18:37 Jakub Narebski <jnareb@gmail.com>:
> > > Having related config variables together is IMVHO more important than
> > > having config variables sorted alphabetically.
> >
> > That's subjective criteria. I doubt there are many related one that
> > can't be handled with standard "see also".
>
> Don't we already have a plan and some patches in flight (from Thomas) to
> turn the master list into a straight one-line-per-config index (which
> probably _should_ be alphabetized), and then put related options into
> their respective manpages (which effectively sorts them by
> functionality)?
Actually Thomas Rast patches (the 'tr/config-doc', not even in 'pu')
are about finding config variables referenced in individual manpages
but not in list of config variables, and adding reference to them in
list of all config variables. Sorting list of variables is orthogonal
to that (though first version sorted by default).
>
> This patch is just going to cause conflicts with Thomas's, and in the
> end will be obsoleted by it.
Could be obsoleted, yes (if we chose sorting). Cause confict, no; at
least if first patch in series is generated by script, as described in
http://permalink.gmane.org/gmane.comp.version-control.git/162145
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-12-01 23:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 13:12 [PATCH] Documentation/config.txt: Order variables alphabetically jari.aalto
2010-12-01 13:58 ` Jakub Narebski
2010-12-01 14:34 ` jari
[not found] ` <20101201142920.GB6537@picasso.cante.net>
2010-12-01 14:57 ` Jakub Narebski
2010-12-01 15:09 ` jari
2010-12-01 15:19 ` Erik Faye-Lund
2010-12-01 15:33 ` Jari Aalto
2010-12-01 15:37 ` Jari Aalto
2010-12-01 16:37 ` Jakub Narebski
2010-12-01 17:10 ` Jari Aalto
2010-12-01 18:03 ` Jeff King
2010-12-01 23:38 ` Jakub Narebski [this message]
2010-12-02 1:02 ` SZEDER Gábor
2010-12-02 5:43 ` Jari Aalto
2010-12-02 9:32 ` SZEDER Gábor
2010-12-02 5:46 ` Jari Aalto
2010-12-02 9:24 ` SZEDER Gábor
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201012020038.55019.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
--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.
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 NNTP newsgroup(s).