git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Krüger" <jk@jk.gs>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org, Kevin Ballard <kevin@sb.org>,
	Junio C Hamano <gitster@pobox.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	Erik Faye-Lund <kusmabite@gmail.com>,
	Jakub Narebski <jnareb@gmail.com>
Subject: Re: [PATCH] git-commit.txt: Order options alphabetically
Date: Thu, 2 Dec 2010 09:53:24 +0100	[thread overview]
Message-ID: <20101202095324.34237fb2@jk.gs> (raw)
In-Reply-To: <87aakpt7uw.fsf@picasso.cante.net>

[Cc un-culled]

--- Jari Aalto <jari.aalto@cante.net> wrote:

> The reader have to guess "imagined groups"? Hm, that's interesting.

Perhaps a more desirable (and agreeable) patch would introduce group
subheadings, then? I agree with the majority of people who chimed in
here that functional grouping is a good thing. Perhaps we should
actually commit to that by having explicit groups.

In rev-list-related options we already have a couple of explicit
groups. I think I'd go insane if I ever had to find anything in there
without those groups.

> [...] Git's command
> line is inconsistent in many places and there is room for improvement.
> Documentation is one way to spot those.

That seems to be the only reason you've brought forward for alphabetic
sorting, except the claim that "people read from top to
bottom" (which is essentially true, but I don't think anybody would
read, say, a printed dictionary all the way through; the alphabetic
ordering there is for being able to index/search the content in the
absence of another way to index/search).

In any case, the end user will probably be more often interested in
appropriately grouped options than in being able to easily find
inconsistencies between various commands.

-Jan

  reply	other threads:[~2010-12-02  8:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 14:58 [PATCH] git-commit.txt: Order options alphabetically jari.aalto
2010-12-01 16:50 ` Jonathan Nieder
2010-12-01 17:16   ` Jari Aalto
2010-12-01 17:48     ` Jakub Narebski
2010-12-01 18:39       ` Jari Aalto
2010-12-02 14:27         ` Jakub Narebski
2010-12-01 19:30     ` Junio C Hamano
2010-12-01 21:58       ` Kevin Ballard
2010-12-01 22:45         ` Jari Aalto
2010-12-01 22:52           ` Kevin Ballard
2010-12-01 23:02             ` Jari Aalto
2010-12-02  8:53               ` Jan Krüger [this message]
2010-12-02 12:03                 ` Jari Aalto
2010-12-02 14:23                   ` Jakub Narebski
2010-12-02 19:30                   ` Jan Krüger
2010-12-01 22:35       ` Jari Aalto
2010-12-01 22:49         ` Kevin Ballard
2010-12-01 23:05           ` Jari Aalto
2010-12-01 23:40             ` Kevin Ballard
2010-12-02  5:35               ` Jari Aalto
2010-12-03 12:10             ` Erik Faye-Lund
2010-12-03 13:03 ` Nguyen Thai Ngoc Duy
  -- strict thread matches above, loose matches on Subject: below --
2010-12-01 15:52 jari.aalto

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=20101202095324.34237fb2@jk.gs \
    --to=jk@jk.gs \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jari.aalto@cante.net \
    --cc=jnareb@gmail.com \
    --cc=jrnieder@gmail.com \
    --cc=kevin@sb.org \
    --cc=kusmabite@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.
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).