[lkml]   [2014]   [Jun]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[PATCH 1/2] Documentation: using git to send patches
From: Dan Carpenter <>

These days most people use git to send patches so I have added a section
about that.

Signed-off-by: Dan Carpenter <>
Signed-off-by: Randy Dunlap <>
v2: fix typo in commit message
v3: update git am and log commands. Mention the man pages.
v4: s/list/appropriate mailing list(s)/

Documentation/email-clients.txt | 11 +++++++++++
1 file changed, 11 insertions(+)

--- lnx-315-rc5.orig/Documentation/email-clients.txt
+++ lnx-315-rc5/Documentation/email-clients.txt
@@ -1,6 +1,17 @@
Email clients info for Linux

+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 the appropriate mailing list(s).
General Preferences
Patches for the Linux kernel are submitted via email, preferably as

 \ /
  Last update: 2014-06-12 19:41    [W:0.042 / U:16.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site