git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junio@pobox.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Gerrit Pape <pape@smarden.org>,
	"Fernando J. Pereda" <ferdy@gentoo.org>,
	git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH amend] git-mailsplit: with maildirs not only process cur/, but also new/
Date: Wed, 07 Nov 2007 18:09:26 -0800	[thread overview]
Message-ID: <7vfxzh7ajt.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071106085418.14211.qmail@54d7c9212e25c5.315fe32.mid.smarden.org> (Gerrit Pape's message of "Tue, 6 Nov 2007 08:54:18 +0000")

Gerrit Pape <pape@smarden.org> writes:

> When saving patches to a maildir with e.g. mutt, the files are put into
> the new/ subdirectory of the maildir, not cur/.  This makes git-am state
> "Nothing to do.".  This patch lets git-mailsplit additional check new/
> after reading cur/.
>
> This was reported by Joey Hess through
>  http://bugs.debian.org/447396
>
> Signed-off-by: Gerrit Pape <pape@smarden.org>
> ---
>
> On Mon, Nov 05, 2007 at 01:58:50PM +0100, Jakub Narebski wrote:
>> > +        for (i = 0; i < 2; ++i) {
>> Wouldn't it be better to use sizeof(sub)/sizeof(sub[0]) or it's macro
>> equivalent ARRAY_SIZE(sub) instead of hardcoding 2 to avoid errors?
> I made the array NULL-terminated.
>
> On Mon, Nov 05, 2007 at 04:26:24PM -0500, Jeff King wrote:
>> Isn't the subject line now wrong?
> Yes, thanks.
>
> On Mon, Nov 05, 2007 at 11:52:58PM +0100, Alex Riesen wrote:
>> Why is missing "cur" (or "new", for that matter) a fatal error?
>> Why is it error at all? How about just ignoring the fact?
> As suggested by Jeff, I made it ignore the error on ENOENT.

Looks good to me.  Final acks please?

  reply	other threads:[~2007-11-08  2:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 14:15 [PATCH] git-mailsplit: with maildirs try to process new/ if cur/ is empty Gerrit Pape
2007-10-26 16:01 ` Fernando J. Pereda
2007-11-05 12:49   ` Gerrit Pape
2007-11-05 12:58     ` Jakub Narebski
2007-11-05 21:26     ` Jeff King
2007-11-05 22:52     ` Alex Riesen
2007-11-06  1:41       ` Michael Cohen
2007-11-06  7:28         ` Alex Riesen
2007-11-06  7:51           ` Jeff King
2007-11-06 11:01             ` Johannes Schindelin
2007-11-06 15:47               ` Jeff King
2007-11-06 15:51                 ` Johannes Schindelin
2007-11-06 16:35                   ` Karl Hasselström
2007-11-06 16:58                     ` Johannes Schindelin
2007-11-06 21:50                     ` Alex Riesen
2007-11-06  8:54       ` [PATCH amend] git-mailsplit: with maildirs not only process cur/, but also new/ Gerrit Pape
2007-11-08  2:09         ` Junio C Hamano [this message]
2007-11-08  2:31           ` Jeff King
2007-11-08  7:24           ` Alex Riesen
2007-11-08  7:31           ` Fernando J. Pereda

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=7vfxzh7ajt.fsf@gitster.siamese.dyndns.org \
    --to=junio@pobox.com \
    --cc=ferdy@gentoo.org \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=pape@smarden.org \
    --cc=peff@peff.net \
    --cc=raa.lkml@gmail.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 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).