diff options
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/email-clients.txt | 11 |
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 @@ | |||
| 1 | Email clients info for Linux | 1 | Email clients info for Linux |
| 2 | ====================================================================== | 2 | ====================================================================== |
| 3 | 3 | ||
| 4 | Git | ||
| 5 | ---------------------------------------------------------------------- | ||
| 6 | These days most developers use `git send-email` instead of regular | ||
| 7 | email clients. The man page for this is quite good. On the receiving | ||
| 8 | end, maintainers use `git am` to apply the patches. | ||
| 9 | |||
| 10 | If you are new to git then send your first patch to yourself. Save it | ||
| 11 | as raw text including all the headers. Run `git am raw_email.txt` and | ||
| 12 | then review the changelog with `git log`. When that works then send | ||
| 13 | the patch to the appropriate mailing list(s). | ||
| 14 | |||
| 4 | General Preferences | 15 | General Preferences |
| 5 | ---------------------------------------------------------------------- | 16 | ---------------------------------------------------------------------- |
| 6 | Patches for the Linux kernel are submitted via email, preferably as | 17 | Patches for the Linux kernel are submitted via email, preferably as |
