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@xxxxxxxxxx>
> ---
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
