Documentation: using git to send patches
Randy Dunlap
reviewerPATCH 1/2 Documentation: using git to send patches
From: Dan Carpenter <[email protected]>
These days most people use git to send patches so I have added a section about that.
Signed-off-by Dan Carpenter <[email protected]>
Signed-off-by Randy Dunlap <[email protected]>
---
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(+)
Documentation/email-clients.txt +11 -0
@@ -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