From: Andreas Schwab <schwab@linux-m68k.org>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Brandon Casey <drafnel@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil>,
jk@silentcow.com, git@vger.kernel.org
Subject: Re: am fails to apply patches for files with CRLF lineendings
Date: Wed, 16 Dec 2009 01:38:20 +0100 [thread overview]
Message-ID: <m2eimvu51f.fsf@igel.home> (raw)
In-Reply-To: <m26387voiy.fsf@igel.home> (Andreas Schwab's message of "Tue, 15 Dec 2009 23:52:05 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
> Björn Steinbrink <B.Steinbrink@gmx.de> writes:
>
>> Right. And checking, after sending a patch containing CRs with mutt, it
>> lost those CRs. Even the local copy saved directly by mutt, which didn't
>> leave my box, lacks the CRs. So it seems basically impossible to send
>> patches to CRLF files inline.
>
> If you want to send mail containing a bare CR you need to encode it.
Btw, this mail had a stray CR added to the last line when I sent it out
(properly encoded as quoted-printable), but that didn't make it through
gmane. :-)
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-12-16 0:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 18:33 am fails to apply patches for files with CRLF lineendings Björn Steinbrink
2009-12-14 20:27 ` Junio C Hamano
2009-12-14 20:34 ` Junio C Hamano
[not found] ` <776A5AB0-E6BC-4230-800E-BE1B7A6B09BF@silentcow.com>
2009-12-14 20:55 ` Björn Steinbrink
2009-12-14 21:16 ` Jason King
2009-12-14 22:56 ` Brandon Casey
2009-12-14 23:22 ` Junio C Hamano
[not found] ` <ee63ef30912141650ie05baf4kab8505adf160c62e@mail.gmail.com>
2009-12-15 1:25 ` Björn Steinbrink
2009-12-15 22:52 ` Andreas Schwab
2009-12-16 0:38 ` Andreas Schwab [this message]
2009-12-15 2:09 ` Fwd: " Brandon Casey
2009-12-15 6:33 ` Sverre Rabbelier
2009-12-15 16:04 ` Brandon Casey
2009-12-15 23:18 ` Fwd: " Andreas Schwab
2009-12-15 2:12 ` Junio C Hamano
2009-12-15 3:59 ` Brandon Casey
[not found] ` <F25E4EFA-BDD8-4920-96FC-2347AD5A3605@silentcow.com>
2010-01-05 16:41 ` Brandon Casey
2010-02-13 19:07 ` Jason King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2eimvu51f.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=B.Steinbrink@gmx.de \
--cc=brandon.casey.ctr@nrlssc.navy.mil \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jk@silentcow.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).