Documentation/email-clients.txt: add a section about git
PATCH v3 1/1 Documentation/email-clients.txt: add a section about git
These days most people use git to send patches so I have added a section about that.
---
v2: fix typo in commit message
v3: update git am and log commands. Mention the man pages.
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 list. + General Preferences ---------------------------------------------------------------------- Patches for the Linux kernel are submitted via email, preferably as
Randy Dunlap
reviewerQuoted 16 lines · Dan Carpenter
These days most people use git to send patches so I have added a section about that.
Signed-off-by Dan Carpenter <[email protected]>---
v2: fix typo in commit message
v3: update git am and log commands. Mention the man pages.Documentation/email-clients.txt +0
-0@@ -1,6 +1,17 @@ Email clients info for Linux ======================================================================
Documentation/email-clients.txt line 13
Quoted 10 lines
Documentation/email-clients.txt +10
-0+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?
Quoted 5 lines
Documentation/email-clients.txt +1
-0+ General Preferences ---------------------------------------------------------------------- Patches for the Linux kernel are submitted via email, preferably as
Signature · 1 line
~Randy
PATCH v4 1/1 Documentation/email-clients.txt: add a section about git
These days most people use git to send patches so I have added a section about that.
---
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 -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
_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Quoted 4 lines · Dan Carpenter
These days most people use git to send patches so I have added a section about that.
Signed-off-by Dan Carpenter <[email protected]>
Applied. Thanks.
Quoted 28 lines
---
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
-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_______________________________________________
Signature · 1 line
~Randy