From: Jakub Narebski Date: Wed, 01 Dec 2010 14:57:29 GMT Subject: Re: [PATCH] Documentation/config.txt: Order variables alphabetically Message-ID: <201012011557.30849.jnareb@gmail.com> In-Reply-To: <20101201142920.GB6537@picasso.cante.net> On Wed, 1 Dec 2010, Jari Aalto wrote: > On 2010-12-01 05:58, Jakub Narebski wrote: > | jari.aalto@cante.net writes: > | > | > From: Jari Aalto > | > > | > > | > Signed-off-by: Jari Aalto > | > --- > | > Documentation/config.txt | 1698 +++++++++++++++++++++++----------------------- > | > 1 files changed, 852 insertions(+), 846 deletions(-) > | > | Why? What such large change is for? > | > | Note that currently config variables are grouped by functionality: for > | example core.eol and core.safecrlf, or core.compression and > | core.loosecompression are close to each other. What about the above? > The phone books have an index where to up information. > > - When you see script and it use VARIABLE, you look it from > manual page Manpages (and 'git --help') are displayed in pager, so you can always search for option in a pager (e.g. '/' in 'less', the default pager). > > It is same as putting option in alphabetical order. See GNU cp(1), > ssh(1) etc. In git documentation command line options are not in alphabetical order, but grouped by functionality, therefore your argument is invalid. See also GNU tar(1), rpm(8), uname(1) from coreutils, etc. > > There are zillion values and for a reference, alphabetical order makes > sense. I agree that alphabetical order makes sense for glossary; I disagree that it makes sense here. Sidenote: we can always sort variables alphabetically using a script, but reverse operation cannot be automated. -- Jakub Narebski Poland