git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: sverre@rabbelier.nl
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Cedric Vivier <cedricv@neonux.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] use natural ordering to display list of branches.
Date: Fri, 06 Jun 2008 21:03:51 +0200	[thread overview]
Message-ID: <48498A17.5000202@gnu.org> (raw)
In-Reply-To: <bd6139dc0806061136o3830c826va416edca16550fa9@mail.gmail.com>

Sverre Rabbelier wrote:
> On Fri, Jun 6, 2008 at 8:11 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>> Except, of course, if you have a script that wants to override whatever
>> the user set in her config.
> 
> I think this is why stuff like GDB has both a CLI and a MI. In order
> to keep the CLI clean you have to make choices, similar to how we
> already separate plumbing from porcelain. I guess in that sense our MI
> is the plumbing, and the porcelain is our CLI. Of course, in that case
> there needn't be such an option in the porcelain, as long as there is
> one in the plumbing ;).
> Conclusion, go for the config option but make sure there's a switch
> for scripts in the plumbing?

Or do the natural sorting only in the porcelain, even if that means 
sorting twice, and use a config option in the porcelain?

(Now, "git branch" is porcelain isn't it?  Plumbing is git-for-each-ref, 
and it has sorting options).

Paolo

  reply	other threads:[~2008-06-06 19:04 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
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 [this message]
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=48498A17.5000202@gnu.org \
    --to=bonzini@gnu.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=cedricv@neonux.com \
    --cc=git@vger.kernel.org \
    --cc=sverre@rabbelier.nl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).