* Adam Piatyszek [17 I 2008 11:10]:
Please find the attached two emails, which show this problem. The
original file (0001-Add-Dolph-Chebyshev-window.patch) was produced with
"git format-patch" from one of my private Git repositories. The other
file (0001-Add-Dolph-Chebyshev-window-sent.patch) includes the same
patch but sent with "git send-email". The problem is with the last hunk,
which is somehow broken by the "git send-email" tool. The very long
lines are wrapped and some exclamation marks are inserted.
The result of applying such a broken patch in my repository is as follows:
===== >8 =====
ediap@lespaul ~/git/itpp $ git am 0001-Add-Dolph-Chebyshev-window-sent.patch
Applying Add Dolph Chebyshev window.
fatal: corrupt patch at line 126
Patch failed at 0001.
When you have resolved this problem run "git-am --resolved".
If you would prefer to skip this patch, instead run "git-am --skip".
===== >8 =====
If I send the same patch with mutt inlined or attached, the patch is not
broken and applies cleanly.
Sorry for the noise! It seems that it is not a problem of "git send-email".
I have just resent this patch to myself once again, this time using mutt
"bounce" function, and it resulted in the broken patch in exactly the
same way.
The incorrect line wrapping with an exclamation mark is exactly at 990
column. Is there any limitation of the line size for text/plain messages?
BR,
/Adam
--
.:. Adam Piatyszek (ediap) .:.....................................:.
.:. ediap@xxxxxxxxxxxxxxxxxxxxx .:................................:.
-
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
