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 <santi@xxxxxxxxxxx> wrote: > > On Sat, Nov 1, 2008 at 8:28 AM, Tom Preston-Werner <tom@xxxxxxxxxx> 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@xxxxxxxxxx> > >> --- > >> 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@xxxxxxxxx > >> + 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@xxxxxxxxxx OOO http://www.madism.org
Attachment:
pgpZsAzdjbGaW.pgp
Description: PGP signature
