From: Randy Dunlap <rdunlap@infradead.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org
Subject: Re: [patch v3] Documentation/email-clients.txt: add a section about git
Date: Wed, 14 May 2014 14:12:49 -0700 [thread overview]
Message-ID: <5373DC51.2080207@infradead.org> (raw)
In-Reply-To: <20140513133200.GA21702@mwanda>
On 05/13/2014 06:32 AM, Dan Carpenter wrote:
> These days most people use git to send patches so I have added a section
> about that.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> v2: fix typo in commit message
> v3: update git am and log commands. Mention the man pages.
>
> diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
> index 4e30eba..9293477 100644
> --- a/Documentation/email-clients.txt
> +++ b/Documentation/email-clients.txt
> @@ -1,6 +1,17 @@
> Email clients info for Linux
> ======================================================================
>
> +Git
> +----------------------------------------------------------------------
> +These days most developers use `git send-email` instead of regular
> +email clients. The man page for this is quite good. On the receiving
> +end, maintainers use `git am` to apply the patches.
> +
> +If you are new to git then send your first patch to yourself. Save it
> +as raw text including all the headers. Run `git am raw_email.txt` and
> +then review the changelog with `git log`. When that works then send
> +the patch to list.
how about:
to the appropriate mailing list(s).
or
to the mailing list(s).
?
I'm not real crazy about this coming before Everything Else in this
text file, but that's what you intended, right?
> +
> General Preferences
> ----------------------------------------------------------------------
> Patches for the Linux kernel are submitted via email, preferably as
>
--
~Randy
next prev parent reply other threads:[~2014-05-14 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 13:32 [patch v3] Documentation/email-clients.txt: add a section about git Dan Carpenter
2014-05-14 21:12 ` Randy Dunlap [this message]
2014-05-15 9:33 ` [patch v4] " Dan Carpenter
2014-05-15 21:01 ` 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=5373DC51.2080207@infradead.org \
--to=rdunlap@infradead.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).