git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Richard Braun <rbraun@sceen.net>,
	Ramkumar Ramachandra <artagnon@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: Maildir ordering in git-mailsplit (was: Using mutt as a git maintainer)
Date: Tue, 10 Aug 2010 19:54:11 +0200	[thread overview]
Message-ID: <20100810175411.GA13084@vidovic> (raw)
In-Reply-To: <m3eieao8uh.fsf@localhost.localdomain>

The 07/08/10, Jakub Narebski wrote:
> Richard Braun <rbraun@sceen.net> writes:
> > 
> > I'm not sure about what depends on string-list.c, but based on the
> > output of a raw grep, it doesn't seem like a good idea to change the
> > way strings are sorted, especially if almost noone uses Maildir for
> > patch series. [...]

I do use maildir but never hit this problem (or never seen it, at least)
probably because I often purge the maildir "_patches" where I store
patch series.

> Would it be really that difficult to implement "version sort" in git
> (like 'ls -v' / 'ls --sort=version' does), using strverscmp (and
> provide fallback in compat/), and use it in git-am?

Yeah, it would be nice to fix this bug. I don't have time these days but
I'm marking this thread to look further later.

-- 
Nicolas Sebrecht

      reply	other threads:[~2010-08-10 17:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100806222847.GA4240@sceen.net>
2010-08-07  2:43 ` Maildir ordering in git-mailsplit (was: Using mutt as a git maintainer) Ramkumar Ramachandra
2010-08-07 11:21   ` Richard Braun
2010-08-07 13:23     ` Jakub Narebski
2010-08-10 17:54       ` Nicolas Sebrecht [this message]

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=20100810175411.GA13084@vidovic \
    --to=nicolas.s.dev@gmx.fr \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=rbraun@sceen.net \
    /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).