From: Jari Aalto <jari.aalto@cante.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/config.txt: Order variables alphabetically
Date: Wed, 01 Dec 2010 19:10:55 +0200 [thread overview]
Message-ID: <87vd3dv2ow.fsf@picasso.cante.net> (raw)
In-Reply-To: 201012011737.53652.jnareb@gmail.com
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".
A small percentage of variables that "group" is bad criteria for general
use. Especially when confix.txt contains somewhere 250 options.
Most of the time you want to look up X. And alpha order is what doctor
ordered.
Same for command line options. You read zillions of scripts and cryptic
options. You want to consult manual page to see what an option means. Again
you're searching A-Z.
Jari
next prev parent reply other threads:[~2010-12-01 17:11 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 [this message]
2010-12-01 18:03 ` Jeff King
2010-12-01 23:38 ` Jakub Narebski
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=87vd3dv2ow.fsf@picasso.cante.net \
--to=jari.aalto@cante.net \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.