From: Junio C Hamano <email@example.com> To: firstname.lastname@example.org Cc: Jonathan Nieder <email@example.com>, Eric Sunshine <firstname.lastname@example.org>, email@example.com, "Robert P. J. Day" <firstname.lastname@example.org> Subject: Re: de-alphabetizing the documentation Date: Mon, 13 Aug 2018 11:17:28 -0700 Message-ID: <email@example.com> (raw) In-Reply-To: <20180811023036.GA19208@ofb.net> (frederik's message of "Fri, 10 Aug 2018 19:30:36 -0700") firstname.lastname@example.org writes: > Hi Jonathan and Git developers, > > I poked around today and figured out how to reorder the command > listings in the manual page, they are taken from git/command-list.txt > so I just reorder the lines in that file (after disabling sorting in > git/Documentation/cmd-list.perl). > > I haven't reordered the whole list yet. I could only get one computer > friend to send me his subcommand frequencies from his shell history. I > reordered the commands partly based on that, and partly based on their > order of occurrence in the various tutorial man pages. There are two good things about a list that is alphabetical. One is that you can scan with your eyes and a finger to find what you are looking for more quickly. The other is that it is mechanical so we won't waste time on bickering whose frequency table is more correct, whether frequency table is a good approach to derive a better order (than, say, the order in which the commands appear in an every-day workflow) to begin with. I would say if we were departing from alphabetical order, we should first declare that we are *not* looking for the best way to order the list, so that people do not waste too much time bikeshedding. Instead what we should aim for is to come up with _an_ order that is not too unreasonable and settle as quickly as we can. And from that point of view, what I saw in new-git.1.out, I found it not so outrageously unreasonable ;-).
next prev parent reply other threads:[~2018-08-13 18:17 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-07-06 20:04 frederik 2018-07-06 21:16 ` Jonathan Nieder 2018-07-06 21:18 ` Jonathan Nieder 2018-07-06 23:21 ` frederik 2018-07-06 23:47 ` Jonathan Nieder 2018-07-08 1:09 ` frederik 2018-07-24 19:52 ` frederik 2018-07-24 21:11 ` Jonathan Nieder 2018-08-11 2:30 ` frederik 2018-08-13 18:17 ` Junio C Hamano [this message] 2019-02-19 17:54 ` [PATCH 0/1] de-alphabetize command list Frederick Eaton 2019-02-21 18:05 ` frederik 2019-03-11 9:04 ` frederik 2019-03-11 14:38 ` Jacob Keller 2019-02-19 17:54 ` [PATCH] Prioritize list of commands appearing in git(1), via command-list.txt. Don't invoke 'sort' in Documentation/cmd-list.perl Frederick Eaton 2018-07-07 4:25 ` de-alphabetizing the documentation Theodore Y. Ts'o 2018-07-06 21:32 ` Eric Sunshine
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
firstname.lastname@example.org list mirror (unofficial, one of many) This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 git git/ https://public-inbox.org/git \ email@example.com public-inbox-index git Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.io/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ code repositories for the project(s) associated with this inbox: https://80x24.org/mirrors/git.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git