From: Aaron Crane <git@aaroncrane.co.uk>
To: git@vger.kernel.org
Subject: Gmail and unwanted line-wrapping
Date: Sat, 6 Feb 2010 20:29:32 +0000 [thread overview]
Message-ID: <bc341e101002061229t7a1525c2w2d5a8e221124b3c2@mail.gmail.com> (raw)
Documentation/SubmittingPatches says this about dealing with Gmail's
propensity for breaking your email:
> GMail does not appear to have any way to turn off line wrapping in the web
> interface, so this will mangle any emails that you send. You can however
> use any IMAP email client to connect to the google imap server, and forward
> the emails through that. Just make sure to disable line wrapping in that
> email client. Alternatively, use "git send-email" instead.
>
> Submitting properly formatted patches via Gmail is simple now that
> IMAP support is available. First, edit your ~/.gitconfig to specify your
> account settings:
<snip>
> Next, ensure that your Gmail settings are correct. In "Settings" the
> "Use Unicode (UTF-8) encoding for outgoing messages" should be checked.
>
> Once your commits are ready to send to the mailing list, run the following
> command to send the patch emails to your Gmail Drafts folder.
>
> $ git format-patch -M --stdout origin/master | git imap-send
>
> Go to your Gmail account, open the Drafts folder, find the patch email, fill
> in the To: and CC: fields and send away!
However, the advice beginning "Submitting properly formatted patches
via Gmail is simple now" doesn't match my experience. Following those
guidelines seemed to work, but my patch was line-wrapped anyway.
It seems I'm not the only person who's observed this:
http://article.gmane.org/gmane.comp.version-control.git/133020
Can anyone think of anything I might have done wrong here? If not,
I'm inclined to suggest dropping all of that advice. That's not
ideal, because it leaves Gmail users with no obvious way to submit
well-formatted patches to the list; but it's better than suggesting
something which apparently doesn't work.
--
Aaron Crane ** http://aaroncrane.co.uk/
next reply other threads:[~2010-02-06 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 20:29 Aaron Crane [this message]
2010-02-06 20:47 ` Gmail and unwanted line-wrapping Sverre Rabbelier
2010-02-07 0:24 ` David Aguilar
2010-02-07 0:50 ` Jay Soffian
2010-02-07 0:51 ` Jay Soffian
2010-02-08 15:20 ` Erik Faye-Lund
2010-02-06 20:49 ` Jacob Helwig
2010-02-06 20:59 ` Sverre Rabbelier
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=bc341e101002061229t7a1525c2w2d5a8e221124b3c2@mail.gmail.com \
--to=git@aaroncrane.co.uk \
--cc=git@vger.kernel.org \
/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).