summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorStephen Rothwell <sfr@canb.auug.org.au>2014-05-27 17:44:30 +1000
committerStephen Rothwell <sfr@canb.auug.org.au>2014-05-27 17:44:30 +1000
commit1af5216fddb92772f7ebc6daa314cb04c8a2aff3 (patch)
treee94fd6a905028b41948feed65b9402e0cb331610 /Documentation
parent1e7c790795b25373dbd3bbd02446b467835f4753 (diff)
parent8b1cbef71a7e83afa78455451d59d96d4228e6a9 (diff)
Merge branch 'rd-docs/master'
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/email-clients.txt11
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
======================================================================
+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 the appropriate mailing list(s).
+
General Preferences
----------------------------------------------------------------------
Patches for the Linux kernel are submitted via email, preferably as