Re: [PATCH] git-commit.txt: Order options alphabetically

From: Jari Aalto <jari.aalto@cante.net>
Date: Dec 1, 2010, 18:39 UTC
Message-ID: <87k4jtuyky.fsf@picasso.cante.net>
In-Reply-To: <m362vd4c6h.fsf@localhost.localdomain>

2010-12-01 19:48 Jakub Narebski <jnareb@gmail.com>:

Show 6 quoted lines

>> 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.

Decresing 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.

I don't mind work. You just watch and lean back.

Show 7 quoted lines

>> 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 chnage 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. Teh copy from fellow worker.

The manual pages main use it as reference material. We don't need to fight the obvious.

Jari