Re: [PATCH 2/2] test mailinfo rfc3676 support

["Jay Soffian" <jaysoffian@gmail.com>]

On Fri, Feb 15, 2008 at 6:01 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>  Hmm.  Such a corrupt patch (lacking spaces at the beginning of the line)
>  would not be accepted by git-apply.  I briefly thought about teaching
>  git-apply to grok that, with a flag.  But now I think that mailsplit
>  should handle that, no?
>
>  Question is: can you "de-corruptify" such a patch? (Note: it would
>  probably need a validating step, too, i.e. count the lines it added a
>  space to, and match that up with the numbers in the @@ lines)

Heh, I see this was a confusing patch. It is a lot clearer to read if
you apply it and then take a look at what's added to sample.mbox, as
well as look at the new files in t5100.

What I did to create this test was add the format=flowed code to
mailinfo (my previous patch email), extract it with format-patch, then
cut/paste it into my MUA and mail it to myself so I could have a sample
format=flowed message. I then added that to the sample.mbox to see if
the code I'd just added to mailinfo was working properly. Yes, it
"de-corrupted" it just fine by removing the flowing.

j.