# [PATCH] add instructions on how to send patches to the mailing list with Gmail 5 messages from 2008-11-01 to 2008-11-02. Participants: Tom Preston-Werner, Santi Béjar, Pierre Habouzit, Fredrik Skolmli. Thread: https://gitlist.dev/t/16120 ## Tom Preston-Werner, 2008-11-01 07:28 Subject: [PATCH] add instructions on how to send patches to the mailing list with Gmail Message-ID: URL: https://gitlist.dev/e/b97024a40811010028l36606128v61172807f4cf503a%40mail.gmail.com ``` 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 --- 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 + +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! -- 1.6.0.2 ``` ## Santi Béjar, 2008-11-01 10:00 Subject: Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail Message-ID: URL: https://gitlist.dev/e/adf1fd3d0811010300ye0aca83t12d271388d35b8d4%40mail.gmail.com In-Reply-To: ``` On Sat, Nov 1, 2008 at 8:28 AM, Tom Preston-Werner 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 > --- > 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. > + > +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? Santi ``` ## Tom Preston-Werner, 2008-11-01 20:40 Subject: Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail Message-ID: URL: https://gitlist.dev/e/b97024a40811011340s92a1c24jb81b75dfb25e43c5%40mail.gmail.com In-Reply-To: ``` On Sat, Nov 1, 2008 at 3:00 AM, Santi Béjar wrote: > On Sat, Nov 1, 2008 at 8:28 AM, Tom Preston-Werner 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 >> --- >> 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 ``` ## Pierre Habouzit, 2008-11-02 09:10 Subject: Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail Message-ID: <20081102091006.GA4066@artemis> URL: https://gitlist.dev/e/20081102091006.GA4066%40artemis In-Reply-To: ``` On Sat, Nov 01, 2008 at 08:40:27PM +0000, Tom Preston-Werner wrote: > On Sat, Nov 1, 2008 at 3:00 AM, Santi Béjar wrote: > > On Sat, Nov 1, 2008 at 8:28 AM, Tom Preston-Werner 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 > >> --- > >> 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. What he means is that the password is cleartext ;) (I think) -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.org ``` ## Fredrik Skolmli, 2008-11-02 15:01 Subject: Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail Message-ID: <20081102150100.GF13242@frsk.net> URL: https://gitlist.dev/e/20081102150100.GF13242%40frsk.net In-Reply-To: <20081102091006.GA4066@artemis> ``` On Sun, Nov 02, 2008 at 10:10:06AM +0100, Pierre Habouzit wrote: > > > 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. > > What he means is that the password is cleartext ;) > (I think) The way I read and understand it, the issues arises if a MITM-attack takes place. If the client doesn't verify the certificate, an attacker can easily get the username and password. So unless someone creates a separate gmail-account for submitting patches, one should really trust the connection (ie not a public wlan), or verify the certificate before transmitting the password. -- Kind regards, Fredrik Skolmli ```