From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nanako Shiraishi <nanako3@lavabit.com>,
Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
git@vger.kernel.org, Stephen Boyd <bebarino@gmail.com>,
Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Subject: [PATCH v6] Re: mailinfo: allow e-mail files as input
Date: Sat, 18 Jul 2009 00:04:24 +0200 [thread overview]
Message-ID: <20090717220424.GA12968@vidovic> (raw)
In-Reply-To: <7vtz1b3x26.fsf@alter.siamese.dyndns.org>
The 17/07/09, Junio C Hamano wrote:
> Nanako Shiraishi <nanako3@lavabit.com> writes:
>
> > Why does this description have ... in it? If I'm reading it correctly, the code in check_patch_format function checks only the first file.
( Please, wrap your lines to something convenient. )
> Good eyes.
>
> This actually is an issue with the Guiseppe's multi-format support patch
> in that we assume that the command line input are of uniform type, check
> only $1 and assume $2 and subsequent are suitable to be fed to the same
> splitter.
>
> I do not think it is necessary to allow mixed input. We certainly could,
> but why bother? It is not a sensible nor common thing to do.
I agree.
> Also the documentation said we take only one mbox or multiple Maildirs,
> but in reality we can take multiple mboxes just fine, so <mbox> should
> have had "..." at the end (we could lose the ellipses from all of them for
> brevity). Oh, and it should list the other formats Giuseppe added.
>
> <mbox>|<maildir>|<email>::
>
> One or more of the same type of mail source to read e-mails
> from. A directory is taken as a mailbox in the maildir
> format. A file is taken as UNIX mbox, StGit patch series
> file, or a single piece of e-mail in RFC2822 format.
Strictly speacking, this is not what I understand from the code: only
one StGit patch series can be given at the command line.
<mbox>|<maildir>|<stgit>|<email>::
One or more of the same type of mail source to read e-mails
from. A directory is taken as a mailbox in the maildir
format. A file is taken as UNIX mbox, StGit patch file,
or a single piece of e-mail in RFC2822 format. StGit
patches series are also supported but only one series at
a time.
--
Nicolas Sebrecht
next prev parent reply other threads:[~2009-07-17 22:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 22:19 [PATCH v3] git-am: fix maildir support regression: accept email file as patch Nicolas Sebrecht
2009-07-15 22:43 ` [PATCH v3] " Nicolas Sebrecht
2009-07-15 22:54 ` [PATCH v3] " Junio C Hamano
2009-07-15 23:56 ` Junio C Hamano
2009-07-16 1:00 ` [PATCH v3] " Nicolas Sebrecht
2009-07-16 2:06 ` Nicolas Sebrecht
2009-07-16 2:30 ` Junio C Hamano
2009-07-16 2:59 ` Nicolas Sebrecht
2009-07-16 0:49 ` Nicolas Sebrecht
2009-07-16 2:41 ` Junio C Hamano
2009-07-16 4:05 ` [PATCH v4] git-am: allow e-mail file(s) as input Nicolas Sebrecht
2009-07-16 4:10 ` [PATCH v4] " Nicolas Sebrecht
2009-07-16 5:23 ` [PATCH v5] " Nicolas Sebrecht
2009-07-16 7:09 ` Stephen Boyd
2009-07-16 7:24 ` Junio C Hamano
2009-07-16 7:50 ` [PATCH v5] " Nicolas Sebrecht
2009-07-16 8:06 ` Nicolas Sebrecht
2009-07-16 8:17 ` Johannes Sixt
2009-07-16 8:12 ` Johannes Sixt
2009-07-16 17:45 ` [PATCH v6] mailinfo: allow e-mail files " Nicolas Sebrecht
2009-07-17 1:05 ` Junio C Hamano
2009-07-17 2:20 ` [PATCH v6] " Nicolas Sebrecht
2009-07-17 10:06 ` [PATCH v6] " Nanako Shiraishi
2009-07-17 19:54 ` Junio C Hamano
2009-07-17 22:04 ` Nicolas Sebrecht [this message]
2009-08-06 17:07 ` [PATCH v7] " Nicolas Sebrecht
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=20090717220424.GA12968@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=giuseppe.bilotta@gmail.com \
--cc=nanako3@lavabit.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).