From: Jakub Narebski <jnareb@gmail.com>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH] git-commit.txt: Order options alphabetically
Date: Thu, 02 Dec 2010 06:27:58 -0800 (PST) [thread overview]
Message-ID: <m3sjyg2qtc.fsf@localhost.localdomain> (raw)
In-Reply-To: <87k4jtuyky.fsf@picasso.cante.net>
Jari Aalto <jari.aalto@cante.net> writes:
> 2010-12-01 19:48 Jakub Narebski <jnareb@gmail.com>:
> > > 2010-12-01 18:50 Jonathan Nieder <jrnieder@gmail.com>:
> >
> > But because some manpages "include" other pages (to refactor common
> > options), it would be impossible to sort alphabetically options in all
> > manpages. So why bother with impossible? It would only introduce
> > inconsistency.
>
> Decreasing entropy is better goal even if we cannot make it perfect. We
> do what we can. And there are many pages that don't use include.
Increasing inconsistency is not good, and that would be the final side
effect.
> I don't mind work. You just watch and lean back.
But we do mind unnecessary code churn (well, in this case documentation
churn). Unless you regard it as "academical" exercise.
The final decision on merging in (accepting) changes lies at git
maintainer.
> > > professional, it looks clean. And it works when searching (= no
> > > orientation problems).
> >
> > It works if you have separate user's documentation from reference
> > documentation. GNU projects were meant to have manpages as reference,
> > and info pages as user's documentation. Options sorted alphabetically
> > might make sense for reference documentation.
>
> It makes sense regardless. Printing literature and how people read and
> search information hasn't changed since printing was invented.
How people search information *has* changed since printing was invented.
> > But git manpages doesn't serve _only_ as reference documentation. And
> > learning commands from manpages where options are sorted alphabetically
> > instead of grouped together by function *suck* big time.
>
> Nope. Manual pages are not where people learn things any more. They
> Google. They buy books. They copy from fellow worker.
>
> The manual pages main use it as reference material. We don't need to
> fight the obvious.
Counterexample: Perl manpages.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-12-02 14:28 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 [this message]
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
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=m3sjyg2qtc.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
--cc=jrnieder@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).