Hi,
On Thu, 14 Feb 2008, Jay Soffian wrote:
> +@@ -20,6 +20,13 @@ static enum {
> +static enum {
> + TYPE_TEXT, TYPE_OTHER,
> +} message_type;
> ++/* RFC 3676 Text/Plain Format and DelSp Parameters */
> ++static enum {
> ++ FORMAT_NONE, FORMAT_FIXED, FORMAT_FLOWED,
> ++} tp_format;
> ++static enum {
> ++ DELSP_NONE, DELSP_YES, DELSP_NO,
> ++} tp_delsp;
> +
> +static char charset[256];
> +static int patch_lines;
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)
Ciao,
Dscho
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
