{"thread":{"id":"16120","subject":"[PATCH] add instructions on how to send patches to the mailing list with Gmail","startedAt":"2008-11-01T07:28:18Z","lastAt":"2008-11-02T15:01:00Z","messageCount":5,"participants":["Tom Preston-Werner","Santi Béjar","Pierre Habouzit","Fredrik Skolmli"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"94537","messageId":"b97024a40811010028l36606128v61172807f4cf503a@mail.gmail.com","threadId":"16120","inReplyTo":null,"subject":"[PATCH] add instructions on how to send patches to the mailing list with Gmail","fromName":"Tom Preston-Werner","fromEmail":"tom@github.com","sentAt":"2008-11-01T07:28:18Z","receivedAt":"2008-11-01T07:28:18Z","isPatch":true,"sender":{"key":"tom@github.com","avatar":"https://gravatar.com/avatar/e38396c4b4d7977fac079a61a1b22c7eca553a9aac50efb1862daac22c65fc58?d=mp&s=160"},"body":"Gmail is one of the most popular email providers in the world. Now that Gmail\nsupports IMAP, sending properly formatted patches via `git imap-send` is\ntrivial. This section in SubmittingPatches explains how to do so.\n\nSigned-off-by: Tom Preston-Werner <tom@github.com>\n---\n Documentation/SubmittingPatches |   27 +++++++++++++++++++++++++++\n 1 files changed, 27 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex a1e9100..f0295c6 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -456,3 +456,30 @@ This should help you to submit patches inline using KMail.\n\n 5) Back in the compose window: add whatever other text you wish to the\n message, complete the addressing and subject fields, and press send.\n+\n+\n+Gmail\n+-----\n+\n+Submitting properly formatted patches via Gmail is simple now that\n+IMAP support is available. First, edit your ~/.gitconfig to specify your\n+account settings:\n+\n+[imap]\n+\tfolder = \"[Gmail]/Drafts\"\n+\thost = imaps://imap.gmail.com\n+\tuser = user@gmail.com\n+\tpass = p4ssw0rd\n+\tport = 993\n+\tsslverify = false\n+\n+Next, ensure that your Gmail settings are correct. In \"Settings\" the\n+\"Use Unicode (UTF-8) encoding for outgoing messages\" should be checked.\n+\n+Once your commits are ready to send to the mailing list, run the following\n+command to send the patch emails to your Gmail Drafts folder.\n+\n+\t$ git format-patch -M --stdout origin/master | git imap-send\n+\n+Go to your Gmail account, open the Drafts folder, find the patch email, fill\n+in the To: and CC: fields and send away!\n-- \n1.6.0.2\n"},{"id":"94539","messageId":"adf1fd3d0811010300ye0aca83t12d271388d35b8d4@mail.gmail.com","threadId":"16120","inReplyTo":"b97024a40811010028l36606128v61172807f4cf503a@mail.gmail.com","subject":"Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail","fromName":"Santi Béjar","fromEmail":"santi@agolina.net","sentAt":"2008-11-01T10:00:05Z","receivedAt":"2008-11-01T10:00:05Z","isPatch":true,"sender":{"key":"santi@agolina.net","avatar":null},"body":"On Sat, Nov 1, 2008 at 8:28 AM, Tom Preston-Werner <tom@github.com> wrote:\n> Gmail is one of the most popular email providers in the world. Now that Gmail\n> supports IMAP, sending properly formatted patches via `git imap-send` is\n> trivial. This section in SubmittingPatches explains how to do so.\n>\n> Signed-off-by: Tom Preston-Werner <tom@github.com>\n> ---\n>  Documentation/SubmittingPatches |   27 +++++++++++++++++++++++++++\n>  1 files changed, 27 insertions(+), 0 deletions(-)\n>\n> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\n> index a1e9100..f0295c6 100644\n> --- a/Documentation/SubmittingPatches\n> +++ b/Documentation/SubmittingPatches\n> @@ -456,3 +456,30 @@ This should help you to submit patches inline using KMail.\n>\n>  5) Back in the compose window: add whatever other text you wish to the\n>  message, complete the addressing and subject fields, and press send.\n> +\n> +\n> +Gmail\n> +-----\n> +\n> +Submitting properly formatted patches via Gmail is simple now that\n> +IMAP support is available. First, edit your ~/.gitconfig to specify your\n> +account settings:\n> +\n> +[imap]\n> +       folder = \"[Gmail]/Drafts\"\n> +       host = imaps://imap.gmail.com\n> +       user = user@gmail.com\n> +       pass = p4ssw0rd\n> +       port = 993\n> +       sslverify = false\n\nWarning: It is not secure.\n\n> +\n> +Next, ensure that your Gmail settings are correct. In \"Settings\" the\n> +\"Use Unicode (UTF-8) encoding for outgoing messages\" should be checked.\n> +\n> +Once your commits are ready to send to the mailing list, run the following\n> +command to send the patch emails to your Gmail Drafts folder.\n> +\n> +       $ git format-patch -M --stdout origin/master | git imap-send\n> +\n> +Go to your Gmail account, open the Drafts folder, find the patch email, fill\n> +in the To: and CC: fields and send away!\n\nAre you sure the mail does not get whitespace damaged?\n\nSanti\n"},{"id":"94591","messageId":"b97024a40811011340s92a1c24jb81b75dfb25e43c5@mail.gmail.com","threadId":"16120","inReplyTo":"adf1fd3d0811010300ye0aca83t12d271388d35b8d4@mail.gmail.com","subject":"Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail","fromName":"Tom Preston-Werner","fromEmail":"tom@github.com","sentAt":"2008-11-01T20:40:27Z","receivedAt":"2008-11-01T20:40:27Z","isPatch":true,"sender":{"key":"tom@github.com","avatar":"https://gravatar.com/avatar/e38396c4b4d7977fac079a61a1b22c7eca553a9aac50efb1862daac22c65fc58?d=mp&s=160"},"body":"On Sat, Nov 1, 2008 at 3:00 AM, Santi Béjar <santi@agolina.net> wrote:\n> On Sat, Nov 1, 2008 at 8:28 AM, Tom Preston-Werner <tom@github.com> wrote:\n>> Gmail is one of the most popular email providers in the world. Now that Gmail\n>> supports IMAP, sending properly formatted patches via `git imap-send` is\n>> trivial. This section in SubmittingPatches explains how to do so.\n>>\n>> Signed-off-by: Tom Preston-Werner <tom@github.com>\n>> ---\n>>  Documentation/SubmittingPatches |   27 +++++++++++++++++++++++++++\n>>  1 files changed, 27 insertions(+), 0 deletions(-)\n>>\n>> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\n>> index a1e9100..f0295c6 100644\n>> --- a/Documentation/SubmittingPatches\n>> +++ b/Documentation/SubmittingPatches\n>> @@ -456,3 +456,30 @@ This should help you to submit patches inline using KMail.\n>>\n>>  5) Back in the compose window: add whatever other text you wish to the\n>>  message, complete the addressing and subject fields, and press send.\n>> +\n>> +\n>> +Gmail\n>> +-----\n>> +\n>> +Submitting properly formatted patches via Gmail is simple now that\n>> +IMAP support is available. First, edit your ~/.gitconfig to specify your\n>> +account settings:\n>> +\n>> +[imap]\n>> +       folder = \"[Gmail]/Drafts\"\n>> +       host = imaps://imap.gmail.com\n>> +       user = user@gmail.com\n>> +       pass = p4ssw0rd\n>> +       port = 993\n>> +       sslverify = false\n>\n> Warning: It is not secure.\n\nIt is true that the certificate is not verified, but since the patches\nare destined for a public mailing list, this does not represent a\nlarge problem.\n\n>> +\n>> +Next, ensure that your Gmail settings are correct. In \"Settings\" the\n>> +\"Use Unicode (UTF-8) encoding for outgoing messages\" should be checked.\n>> +\n>> +Once your commits are ready to send to the mailing list, run the following\n>> +command to send the patch emails to your Gmail Drafts folder.\n>> +\n>> +       $ git format-patch -M --stdout origin/master | git imap-send\n>> +\n>> +Go to your Gmail account, open the Drafts folder, find the patch email, fill\n>> +in the To: and CC: fields and send away!\n>\n> Are you sure the mail does not get whitespace damaged?\n\nYes, I have sent patches using exactly this method. Here is an example\nof one I sent today:\nhttp://article.gmane.org/gmane.comp.version-control.git/99759. Tabs\nare preserved and lines are not wrapped improperly.\n\nTom\n"},{"id":"94639","messageId":"20081102091006.GA4066@artemis","threadId":"16120","inReplyTo":"b97024a40811011340s92a1c24jb81b75dfb25e43c5@mail.gmail.com","subject":"Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail","fromName":"Pierre Habouzit","fromEmail":"madcoder@debian.org","sentAt":"2008-11-02T09:10:06Z","receivedAt":"2008-11-02T09:10:06Z","isPatch":true,"sender":{"key":"madcoder@debian.org","avatar":"https://avatars.githubusercontent.com/u/44708?v=4"},"body":"On Sat, Nov 01, 2008 at 08:40:27PM +0000, Tom Preston-Werner wrote:\n> On Sat, Nov 1, 2008 at 3:00 AM, Santi Béjar <santi@agolina.net> wrote:\n> > On Sat, Nov 1, 2008 at 8:28 AM, Tom Preston-Werner <tom@github.com> wrote:\n> >> Gmail is one of the most popular email providers in the world. Now that Gmail\n> >> supports IMAP, sending properly formatted patches via `git imap-send` is\n> >> trivial. This section in SubmittingPatches explains how to do so.\n> >>\n> >> Signed-off-by: Tom Preston-Werner <tom@github.com>\n> >> ---\n> >>  Documentation/SubmittingPatches |   27 +++++++++++++++++++++++++++\n> >>  1 files changed, 27 insertions(+), 0 deletions(-)\n> >>\n> >> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\n> >> index a1e9100..f0295c6 100644\n> >> --- a/Documentation/SubmittingPatches\n> >> +++ b/Documentation/SubmittingPatches\n> >> @@ -456,3 +456,30 @@ This should help you to submit patches inline using KMail.\n> >>\n> >>  5) Back in the compose window: add whatever other text you wish to the\n> >>  message, complete the addressing and subject fields, and press send.\n> >> +\n> >> +\n> >> +Gmail\n> >> +-----\n> >> +\n> >> +Submitting properly formatted patches via Gmail is simple now that\n> >> +IMAP support is available. First, edit your ~/.gitconfig to specify your\n> >> +account settings:\n> >> +\n> >> +[imap]\n> >> +       folder = \"[Gmail]/Drafts\"\n> >> +       host = imaps://imap.gmail.com\n> >> +       user = user@gmail.com\n> >> +       pass = p4ssw0rd\n> >> +       port = 993\n> >> +       sslverify = false\n> >\n> > Warning: It is not secure.\n> \n> It is true that the certificate is not verified, but since the patches\n> are destined for a public mailing list, this does not represent a\n> large problem.\n\nWhat he means is that the password is cleartext ;)\n(I think)\n\n\n-- \n·O·  Pierre Habouzit\n··O                                                madcoder@debian.org\nOOO                                                http://www.madism.org\n"},{"id":"94663","messageId":"20081102150100.GF13242@frsk.net","threadId":"16120","inReplyTo":"20081102091006.GA4066@artemis","subject":"Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail","fromName":"Fredrik Skolmli","fromEmail":"fredrik@frsk.net","sentAt":"2008-11-02T15:01:00Z","receivedAt":"2008-11-02T15:01:00Z","isPatch":true,"sender":{"key":"fredrik@frsk.net","avatar":"https://avatars.githubusercontent.com/u/40261?v=4"},"body":"On Sun, Nov 02, 2008 at 10:10:06AM +0100, Pierre Habouzit wrote:\n\n> > > Warning: It is not secure.\n> > \n> > It is true that the certificate is not verified, but since the patches\n> > are destined for a public mailing list, this does not represent a\n> > large problem.\n> \n> What he means is that the password is cleartext ;)\n> (I think)\n\nThe way I read and understand it, the issues arises if a MITM-attack takes\nplace.  If the client doesn't verify the certificate, an attacker can easily\nget the username and password. \n\nSo unless someone creates a separate gmail-account for submitting patches,\none should really trust the connection (ie not a public wlan), or verify the\ncertificate before transmitting the password.\n\n-- \nKind regards,\nFredrik Skolmli\n"}]}