From: Marius Storm-Olsen <marius@trolltech.com>
To: Cedric Vivier <cedricv@neonux.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] use natural ordering to display list of branches.
Date: Thu, 05 Jun 2008 22:36:18 +0200 [thread overview]
Message-ID: <48484E42.8050209@trolltech.com> (raw)
In-Reply-To: <d45085aa0806051308y16bcca95xad126022fd3ee053@mail.gmail.com>
Cedric Vivier said the following on 05.06.2008 22:08:
> On Thu, Jun 5, 2008 at 8:47 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>> What about people preferring the status quo? I think a command
>> line option would be in order.
>
> Is there really people preferring the status quo ? ;) Of course we
> probably need some debate about making it default or not but you're
> completely right there should be an option about that - and maybe a
> config variable as well? How about
> --sort=ascending|descending|natural (with branch.sort as the
> corresponding config var) ?
IMO, we now need to step back, and start considering the ever
expanding complexity of all the Git command line options. Is there
_really_ a need for a command line option to control this? Will people
_really_, for that _one_ invocation change the order of file listing?
Or, will they simply prefer one particular order, set it, and forget it?
We really need to analyze the use-cases, and do everything we can to
avoid confusing clutter.
IMO this feature falls into the "configuration-variable, but not
command-line option" category. (People who _really_ want a different
order, for that _one_ invocation, are most probable also in the group
that can write their own little 3-line script to do this.)
Just my 10NOK..
--
.marius
next prev parent reply other threads:[~2008-06-05 20:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 17:41 [PATCH] use natural ordering to display list of branches Cedric Vivier
2008-06-05 18:47 ` Johannes Schindelin
2008-06-05 19:29 ` Junio C Hamano
2008-06-05 19:43 ` Johannes Schindelin
2008-06-05 20:08 ` Cedric Vivier
2008-06-05 20:36 ` Marius Storm-Olsen [this message]
2008-06-06 16:46 ` Paolo Bonzini
2008-06-06 18:11 ` Johannes Schindelin
2008-06-06 18:36 ` Sverre Rabbelier
2008-06-06 19:03 ` Paolo Bonzini
2008-06-06 21:04 ` Brandon Casey
2008-06-06 21:17 ` Cedric Vivier
2008-06-06 21:23 ` Brandon Casey
2008-06-06 23:06 ` Johannes Schindelin
2008-06-06 23:11 ` Junio C Hamano
2008-06-06 23:13 ` Asheesh Laroia
2008-06-07 4:42 ` Jeff King
2008-06-07 0:13 ` Cedric Vivier
2008-06-07 0:17 ` Junio C Hamano
2008-06-07 0:43 ` Cedric Vivier
2008-06-07 6:53 ` Junio C Hamano
2008-06-06 21:46 ` しらいしななこ
2008-06-15 23:26 ` Ask Bjørn Hansen
2008-06-06 8:42 ` Mike Ralphson
2008-06-06 8:54 ` Cedric Vivier
2008-06-06 9:06 ` Mike Ralphson
2008-06-09 8:00 ` Andreas Ericsson
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=48484E42.8050209@trolltech.com \
--to=marius@trolltech.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=cedricv@neonux.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.