All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Hillf Danton <dhillf@gmail.com>
Cc: Julian Andres Klode <jak@jak-linux.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	devel@driverdev.osuosl.org, LKML <linux-kernel@vger.kernel.org>,
	linux-doc@vger.kernel.org
Subject: Re: [patch v2] Documentation/email-clients.txt: add a section about git
Date: Fri, 9 May 2014 10:28:01 +0300	[thread overview]
Message-ID: <20140509072801.GI26890@mwanda> (raw)
In-Reply-To: <CAJd=RBBNbJnTsu=73o9Yy4dgVw2zUJR9Cc5=eZB+U+WqJ=4KDg@mail.gmail.com>

On Thu, May 08, 2014 at 05:28:46PM +0800, Hillf Danton wrote:
> And a howto to tame gmail is doule apprecaited.

There is actually a gmail section in the man page.  `man git send-email`
It's a the bottom.


EXAMPLE
   Use gmail as the smtp server
       To use git send-email to send your patches through the GMail SMTP
       server, edit ~/.gitconfig to specify your account settings:

           [sendemail]
                   smtpencryption = tls
                   smtpserver = smtp.gmail.com
                   smtpuser = yourname@gmail.com
                   smtpserverport = 587

       Once your commits are ready to be sent to the mailing list, run the
       following commands:

           $ git format-patch --cover-letter -M origin/master -o outgoing/
           $ edit outgoing/0000-*
           $ git send-email outgoing/*

       Note: the following perl modules are required Net::SMTP::SSL,
       MIME::Base64 and Authen::SASL


regards,
dan carpenter

  reply	other threads:[~2014-05-09  7:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 11:17 [patch] Documentation/email-clients.txt: add a section about git Dan Carpenter
2014-05-07 16:06 ` Laura Abbott
2014-05-07 16:18   ` Dan Carpenter
2014-05-08  8:44   ` [patch v2] " Dan Carpenter
2014-05-08  9:05     ` Julian Andres Klode
2014-05-08  9:28       ` Hillf Danton
2014-05-09  7:28         ` Dan Carpenter [this message]
2014-05-09  0:24     ` Namhyung Kim
2014-05-09  7:26       ` Dan Carpenter
2014-05-11  0:19     ` Randy Dunlap

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=20140509072801.GI26890@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dhillf@gmail.com \
    --cc=jak@jak-linux.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.