[PATCH] Re: git-am: less strong format "mbox" detection

[Nicolas Sebrecht <nicolas.s.dev@gmx.fr>]

The 14/07/09, Junio C Hamano wrote:

> Nicolas Sebrecht <nicolas.s.dev@gmx.fr> writes:
> 
> > And why should we accept "From "?
> 
> You are going totally in a wrong way around with this.
> 
> Berkeley mbox format is what we support, and "From " is the _only_
> delimiter between pieces of e-mail in the file.  We happen to allow "From:
> " in order to merely be extra nice for people who create mbox looking file
> by hand; I think it is an improvement not to require an optional SP after
> the colon there, but that is totally an independent issue.

I see, thank you.

> I cannot offhand say if allowing anything but "From:" is necessarily an
> improvement, or making the format detection unnecessarily risky of
> misidentification.  I do not particularly like the idea of allowing only
> some randomly selected fields like Return-Path and Delibered-To and not
> accepting others, let alone totally nonstandard X-Foo fields.

I'll look at the source closer to know how it can be done the smart way.

As the manual of git-am says it accepts maildir format too (checked
now), we have a regression since

	a5a6755a1d4707bf2fab7752e5c974ebf63d086a

in case of maildir _and_ "verbatim" emails starting with anything else that
"From " or "From: ".

I think the RFC doesn't require any fixed order for the header fields
(will check). So, I'm not very optimist because format detection starts
with

	read l1
	read l2
	read l3

wich doesn't help to make a difference between mailbox and maildir.


-- 
Nicolas Sebrecht