path: root/Documentation
diff options
authorDan Carpenter <dan.carpenter@oracle.com>2014-06-27 18:28:46 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2014-06-29 13:38:33 -0700
commit7d19e91b5220227814e9e875460c2c22c9660a5c (patch)
treeb591ca2c074cca731336e490721b8223d9196836 /Documentation
parent24b414d5a7d3e6a716350464dfdb44da610ed142 (diff)
Documentation: add section about git to email-clients.txt
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> Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation')
1 files changed, 11 insertions, 0 deletions
diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index 4e30ebaa9e5b..9af538be3751 100644
--- a/Documentation/email-clients.txt
+++ b/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

Privacy Policy