git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Documentation/SubmittingPatches: Clarify Gmail section

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Apr 7, 2010, 19:33 UTC
Message-ID
<1270668793-2187-2-git-send-email-artagnon@gmail.com>
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
Previous: Ramkumar RamachandraNext: Junio C Hamano
Message 2 of 7 in “Documentation/SubmittingPatches: Clarify Gmail section”
  1. Documentation/SubmittingPatches: Clarify Gmail sectionRamkumar Ramachandra, Apr 7, 2010
  2. Documentation/SubmittingPatches: Clarify Gmail sectionRamkumar Ramachandra, Apr 7, 2010
  3. Junio C HamanoApr 7, 2010
  4. Jacob HelwigApr 7, 2010
  5. Ramkumar RamachandraApr 7, 2010
  6. Jon SeymourApr 7, 2010
  7. Junio C HamanoApr 7, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.