From: "Cedric Vivier" <cedricv@neonux.com>
To: "Brandon Casey" <casey@nrlssc.navy.mil>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Paolo Bonzini" <bonzini@gnu.org>,
git@vger.kernel.org
Subject: Re: [PATCH] use natural ordering to display list of branches.
Date: Fri, 6 Jun 2008 23:17:30 +0200 [thread overview]
Message-ID: <d45085aa0806061417ue3f1f51i6580acbb51070e5b@mail.gmail.com> (raw)
In-Reply-To: <Jx4nZtFGdU-iUxlX24G6lzMyWe99Z53jtjQp9T9qkMJ1iZC0eZW6xg@cipher.nrlssc.navy.mil>
On Fri, Jun 6, 2008 at 11:04 PM, Brandon Casey <casey@nrlssc.navy.mil> wrote:
> But can't that be just as easily done by piping through sort? (I understand
> there is a platform which lacks the sort utility, boohoo)
Yes, but sort does not have a natural sort option afaik.
If natural sort is the default order though then piping through sort
to get things in "non-natural" order is easy enough indeed.
next prev parent reply other threads:[~2008-06-06 21:18 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
2008-06-06 21:04 ` Brandon Casey
2008-06-06 21:17 ` Cedric Vivier [this message]
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=d45085aa0806061417ue3f1f51i6580acbb51070e5b@mail.gmail.com \
--to=cedricv@neonux.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=bonzini@gnu.org \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
/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).