From: Clemens Ladisch <clemens@ladisch.de>
To: Steve French <smfrench@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Line endings now altered when saving kernel patches via gmail
Date: Thu, 03 May 2012 12:45:23 +0200 [thread overview]
Message-ID: <4FA261C3.6030403@ladisch.de> (raw)
In-Reply-To: <CAH2r5mt8XwHQ5Q-BfpxBp2o5=guafNtxGcEvFcLRTu7EwZjMJg@mail.gmail.com>
Steve French wrote:
> I noticed sometime in the last month that one of the normal patch
> processes (open up gmail, find the email that contains the patch, then
> "show original" then "save as ...") doesn't work anymore. Gmail
> appears to now corrupt patches by inserting DOS line endings (at
> least) even when "show original" - any idea how to turn this off.
SMTP mails always use CR/LF line endings in the body. If the older
gmail did not show them in the source view, this was a bug, which
has now been fixed.
Tools like "git am" automatically convert line endings from mail
to Unix. If your tools don't handle this, you'll have to convert
the files manually after saving them.
Regards,
Clemens
prev parent reply other threads:[~2012-05-03 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 19:58 Line endings now altered when saving kernel patches via gmail Steve French
2012-05-03 10:45 ` Clemens Ladisch [this message]
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=4FA261C3.6030403@ladisch.de \
--to=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@gmail.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