From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
John Tapsell <johnflux@gmail.com>,
Aaron Crane <git@aaroncrane.co.uk>,
A Large Angry SCM <gitzilla@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: [PATCH] Documentation/SubmittingPatches: Clarify Gmail section
Date: Thu, 8 Apr 2010 01:03:13 +0530 [thread overview]
Message-ID: <1270668793-2187-2-git-send-email-artagnon@gmail.com> (raw)
In-Reply-To: <1270668793-2187-1-git-send-email-artagnon@gmail.com>
The web interface mangles patches no matter what. Replace paragraph
about "git imap-send" with another one about "git send-email".
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
Documentation/SubmittingPatches | 53 +++++++++++++++-----------------------
1 files changed, 21 insertions(+), 32 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index c686f86..8193a5b 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -517,35 +517,24 @@ message, complete the addressing and subject fields, and press send.
Gmail
-----
-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:
-
-[imap]
- folder = "[Gmail]/Drafts"
- host = imaps://imap.gmail.com
- user = user@gmail.com
- pass = p4ssw0rd
- port = 993
- sslverify = false
-
-You might need to instead use: folder = "[Google Mail]/Drafts" if you get an error
-that the "Folder doesn't exist".
-
-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!
-
+GMail does not have any way to turn off line wrapping in the web
+interface, so this will mangle any emails that you send. You can
+either configure an email client that that doesn't break lines to use
+the GMail SMTP server, or use "git send-email" to achieve the same
+effect.
+
+To use "git send-email", edit ~/.gitconfig to specify your account
+settings:
+
+[sendemail]
+ smtpencryption = tls
+ smtpserver = smtp.gmail.com
+ smtpuser = user@gmail.com
+ smtppass = p4ssw0rd
+ smtpserverport = 587
+
+Once your commits are ready to send to the mailing list, run the
+following commands:
+
+ $ git format-patch --no-color -C -M origin/master -o outgoing/
+ $ git send-email --compose outgoing/*
--
1.7.0.3
next prev parent reply other threads:[~2010-04-07 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 19:33 [PATCH v2] Documentation/SubmittingPatches: Clarify Gmail section Ramkumar Ramachandra
2010-04-07 19:33 ` Ramkumar Ramachandra [this message]
2010-04-07 20:02 ` [PATCH] " Junio C Hamano
2010-04-07 20:06 ` Jacob Helwig
2010-04-07 20:18 ` Ramkumar Ramachandra
2010-04-07 22:23 ` Jon Seymour
2010-04-07 22:59 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2010-04-07 17:52 Ramkumar Ramachandra
2010-04-07 18:08 ` Ramkumar Ramachandra
2010-04-07 19:09 ` Junio C Hamano
2010-04-07 20:00 ` Ramkumar Ramachandra
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=1270668793-2187-2-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@aaroncrane.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gitzilla@gmail.com \
--cc=johnflux@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;
as well as URLs for NNTP newsgroup(s).