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

Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail

From
Tom Preston-Werner <tom@github.com>
Date
Nov 1, 2008, 20:40 UTC
Message-ID
<b97024a40811011340s92a1c24jb81b75dfb25e43c5@mail.gmail.com>
In-Reply-To
<adf1fd3d0811010300ye0aca83t12d271388d35b8d4@mail.gmail.com>
On Sat, Nov 1, 2008 at 3:00 AM, Santi Béjar <santi@agolina.net> wrote:
Show 36 quoted lines
> On Sat, Nov 1, 2008 at 8:28 AM, Tom Preston-Werner <tom@github.com> wrote:
>> Gmail is one of the most popular email providers in the world. Now that Gmail
>> supports IMAP, sending properly formatted patches via `git imap-send` is
>> trivial. This section in SubmittingPatches explains how to do so.
>>
>> Signed-off-by: Tom Preston-Werner <tom@github.com>
>> ---
>>  Documentation/SubmittingPatches |   27 +++++++++++++++++++++++++++
>>  1 files changed, 27 insertions(+), 0 deletions(-)
>>
>> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
>> index a1e9100..f0295c6 100644
>> --- a/Documentation/SubmittingPatches
>> +++ b/Documentation/SubmittingPatches
>> @@ -456,3 +456,30 @@ This should help you to submit patches inline using KMail.
>>
>>  5) Back in the compose window: add whatever other text you wish to the
>>  message, complete the addressing and subject fields, and press send.
>> +
>> +
>> +Gmail
>> +-----
>> +
>> +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
>
> Warning: It is not secure.

It is true that the certificate is not verified, but since the patches are destined for a public mailing list, this does not represent a large problem.

Show 13 quoted lines
>> +
>> +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!
>
> Are you sure the mail does not get whitespace damaged?

Yes, I have sent patches using exactly this method. Here is an example of one I sent today: http://article.gmane.org/gmane.comp.version-control.git/99759. Tabs are preserved and lines are not wrapped improperly.

Tom
Previous: Santi BéjarNext: Pierre Habouzit
Message 3 of 5 in “add instructions on how to send patches to the mailing list with Gmail”
  1. add instructions on how to send patches to the mailing list with GmailTom Preston-Werner, Nov 1, 2008
  2. Santi BéjarNov 1, 2008
  3. Tom Preston-WernerNov 1, 2008
  4. Pierre HabouzitNov 2, 2008
  5. Fredrik SkolmliNov 2, 2008

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.