git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Jakub Narebski <jnareb@gmail.com>
Date
Dec 2, 2010, 14:27 UTC
Message-ID
<m3sjyg2qtc.fsf@localhost.localdomain>
In-Reply-To
<87k4jtuyky.fsf@picasso.cante.net>
Jari Aalto <jari.aalto@cante.net> writes:
Show 10 quoted lines
> 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.
Show 10 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 changed since printing was invented.
How people search information *has* changed since printing was invented.
Show 9 quoted lines
> > 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
Previous: Jari AaltoNext: Junio C Hamano
Message 6 of 22 in “git-commit.txt: Order options alphabetically”
  1. git-commit.txt: Order options alphabeticallyjari.aalto@cante.net, Dec 1, 2010
  2. Jonathan NiederDec 1, 2010
  3. Jari AaltoDec 1, 2010
  4. Jakub NarebskiDec 1, 2010
  5. Jari AaltoDec 1, 2010
  6. Jakub NarebskiDec 2, 2010
  7. Junio C HamanoDec 1, 2010
  8. Kevin BallardDec 1, 2010
  9. Jari AaltoDec 1, 2010
  10. Kevin BallardDec 1, 2010
  11. Jari AaltoDec 1, 2010
  12. Jan KrügerDec 2, 2010
  13. Jari AaltoDec 2, 2010
  14. Jakub NarebskiDec 2, 2010
  15. Jan KrügerDec 2, 2010
  16. Jari AaltoDec 1, 2010
  17. Kevin BallardDec 1, 2010
  18. Jari AaltoDec 1, 2010
  19. Kevin BallardDec 1, 2010
  20. Jari AaltoDec 2, 2010
  21. Erik Faye-LundDec 3, 2010
  22. Nguyen Thai Ngoc DuyDec 3, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.