From: "Tom Preston-Werner" <tom@github.com>
To: "Santi Béjar" <santi@agolina.net>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail
Date: Sat, 1 Nov 2008 13:40:27 -0700 [thread overview]
Message-ID: <b97024a40811011340s92a1c24jb81b75dfb25e43c5@mail.gmail.com> (raw)
In-Reply-To: <adf1fd3d0811010300ye0aca83t12d271388d35b8d4@mail.gmail.com>
On Sat, Nov 1, 2008 at 3:00 AM, Santi Béjar <santi@agolina.net> wrote:
> 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.
>> +
>> +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
next prev parent reply other threads:[~2008-11-01 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 7:28 [PATCH] add instructions on how to send patches to the mailing list with Gmail Tom Preston-Werner
2008-11-01 10:00 ` Santi Béjar
2008-11-01 20:40 ` Tom Preston-Werner [this message]
2008-11-02 9:10 ` Pierre Habouzit
2008-11-02 15:01 ` Fredrik Skolmli
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=b97024a40811011340s92a1c24jb81b75dfb25e43c5@mail.gmail.com \
--to=tom@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=santi@agolina.net \
/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).