public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, Laura Abbott <lauraa@codeaurora.org>
Subject: Re: [patch v2] Documentation/email-clients.txt: add a section about git
Date: Sat, 10 May 2014 17:19:58 -0700	[thread overview]
Message-ID: <536EC22E.2020802@infradead.org> (raw)
In-Reply-To: <20140508084412.GA20398@mwanda>

On 05/08/2014 01:44 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: Fixed changelog
> 
> diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
> index 4e30eba..9004a5fd 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.  On the receiving end, maintainers use `git am` to
> +apply the patches.
> +

Why is there nothing here about how to use 'git send-email' to send patches?


> +If you are new to git then send your first patch to yourself.  Save it
> +as raw text including all the headers.  Run `cat raw_email.txt | git am`
> +and then review the changelog with `git log -p`.  When that works then
> +send the patch to list.
> +
>  General Preferences
>  ----------------------------------------------------------------------
>  Patches for the Linux kernel are submitted via email, preferably as


-- 
~Randy

      parent reply	other threads:[~2014-05-11  0:20 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
2014-05-09  0:24     ` Namhyung Kim
2014-05-09  7:26       ` Dan Carpenter
2014-05-11  0:19     ` Randy Dunlap [this message]

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=536EC22E.2020802@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=lauraa@codeaurora.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