On Wed, Dec 1, 2010 at 4:09 PM, jari <jari.aalto@xxxxxxxxx> wrote: > On 2010-12-01 15:57, Jakub Narebski wrote: > | On Wed, 1 Dec 2010, Jari Aalto wrote: > | > The phone books have an index where to up information. > | > > | > - When you see script and it use VARIABLE, you look it from > | > manual page > | > | Manpages (and 'git <cmd> --help') are displayed in pager, so you can > | always search for option in a pager (e.g. '/' in 'less', the default > | pager). > > Yuck, it's real fun start backward/forward ping-pong when you dont' > know the directions and can't rely on standard A-Z index. > ...but for config options, I tend to ping-pong between items that are related to each other, which are already located close by. Your argument weighs more for keeping the current layout, IMO. > | > It is same as putting option in alphabetical order. See GNU cp(1), > | > ssh(1) etc. > | > | In git documentation command line options are not in alphabetical order, > | but grouped by functionality, therefore your argument is invalid. > > I see that only in pages that have tens and tens and tens of options.. > > The problem is more the asciidoc's. Various bits and pices are > "included" in place and make orderign the options impossile in some > pages. > > Let's get all pages in shape with A-Z in this regard. That's a god > quality goal. > I still haven't heard a compelling argument why alphabetical ordering is better than logical ordering... -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html