On Sat May 28 18:40:03 2011, yoduh wrote: > New item shows git-send-email configuration setup, with example > showing port, etc for use with a gmail account. > --- > pod/perlhack.pod | 16 ++++++++++++++++ > 1 files changed, 16 insertions(+), 0 deletions(-) > > diff --git a/pod/perlhack.pod b/pod/perlhack.pod > index f8f8bdd..2173e5d 100644 > --- a/pod/perlhack.pod > +++ b/pod/perlhack.pod > @@ -66,6 +66,22 @@ The perlbug program will ask you a few questions > about your email > address and the patch you're submitting. Once you've answered them > you > can submit your patch. > > +=item * Sending patches with git-send-email > + > +Adding the following stanza to your .git/config will tell > +git-send-email where to send and how. For Gmail users, this is very > +nice, as the patches are inlined for easy review, but avoid > whitespace > +mangling thats mostly unavoidable with the web-interface. > +See git help send-email for more. > + > + [sendemail] > + to = perlbug@perl.org > + smtpencryption = tls > + smtpserver = smtp.gmail.com > + smtpuser = <your-gmail-acct> > + smtpserverport = 587 > + # smtppass = <secret> > + Do we really want to promote git-send-email? Whenever anyone uses it, I have to copy and paste things together to recreate something that git-am can understand. If the entire output from git-format-patch is sent as an attachment, only then is it really easy to apply patches.Thread Previous