Hi, On Mon, May 09, 2016 at 10:39:24PM +0200, Jens Neuhalfen wrote: > > - not sure what it is, but it's usually fixed by "git send-email"... thanks. > > strange, I use "git format-patch". I guess that "git am??? gets confused > about the ???duplicate" Subject/From/.. lines (mail header and patch header). > > I???ll switch to send-email
It wasn't the duplicate Subject/From lines, but the whitespace mangling -
which is something mail clients *love* to do, and git send-email knows
how to avoid.
It was not only "git am" - I tried with plain old "patch -p1 <$file",
and that first barfed about "invalid patch", and after I fixed the
lines that had no space in the first column, complained about "does not
apply" because the context was not matching - "patch -l" (ignore
whitespace) worked, and that's a fairly good hint that a mail client
messed up whitespace...
Note: if you use exchange as your outbound mail server, even git send-email
will fail, because exchange *loves* to "fix" leading tabs in mails - Heiko
ran into this a while ago.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
