]>
Commit | Line | Data |
---|---|---|
c93e2eec AC |
1 | Name |
2 | Contributing - instructions for contributing to the project | |
974845c5 | 3 | |
c93e2eec | 4 | Synopsis |
315cc123 | 5 | Mailing list, patches, lint & check, style guide, bug reports, |
3e7901ff | 6 | and more. |
974845c5 | 7 | |
c93e2eec AC |
8 | Description |
9 | Mailing list | |
315cc123 AC |
10 | The main discussions regarding development of the project, |
11 | patches, bugs, news, doubts, etc. happen on the mailing list. | |
12 | To send an email to the project, send it to Alejandro and CC the | |
13 | mailing list: | |
0fd4a9ef | 14 | |
c93e2eec | 15 | To: Alejandro Colomar <alx@kernel.org> |
c93e2eec | 16 | Cc: <linux-man@vger.kernel.org> |
0fd4a9ef | 17 | |
315cc123 AC |
18 | Please CC any relevant developers and mailing lists that may know |
19 | about or be interested in the discussion. If your email | |
20 | discusses a feature or change, and you know which developers | |
21 | added the feature or made the change that your email discusses, | |
22 | please CC them on the email; with luck they may review and | |
23 | comment on it. If you don't know who the developers are, you may | |
24 | be able to discover that information from mailing list archives | |
25 | or from git(1) logs or logs in other version control systems. | |
26 | Obviously, if you are the developer of the feature being | |
27 | discussed in a man-pages email, please identify yourself as such. | |
c93e2eec | 28 | Relevant mailing lists may include: |
0fd4a9ef | 29 | |
c93e2eec | 30 | Cc: LKML <linux-kernel@vger.kernel.org> |
ab5a1258 | 31 | Cc: Linux API <linux-api@vger.kernel.org> |
c93e2eec AC |
32 | Cc: Glibc <libc-alpha@sourceware.org> |
33 | ||
315cc123 AC |
34 | For other kernel mailing lists and maintainers, check the |
35 | <MAINTAINERS> file in the Linux kernel repository. | |
c93e2eec AC |
36 | |
37 | Please don't send HTML email; it will be discarded by the list. | |
38 | ||
39 | Archives: | |
40 | <https://lore.kernel.org/linux-man/> | |
41 | <https://marc.info/?l=linux-man> | |
42 | ||
43 | Subscription: | |
b6ddb894 | 44 | It is not necessary to subscribe to the list to send an |
f5166051 AC |
45 | email. For subscribing to the list, or information about |
46 | it, go to | |
47 | <https://subspace.kernel.org/vger.kernel.org.html>. | |
c93e2eec | 48 | |
3c378b9e | 49 | Sign your emails with PGP |
4b7ae5e6 AC |
50 | We encourage that you sign all of your emails sent to the |
51 | mailing list, (especially) including the ones containing | |
3c378b9e AC |
52 | patches, with your PGP key. This helps establish trust between |
53 | you and other contributors of this project, and prevent others | |
54 | impersonating you. If you don't have a key, it's not mandatory | |
55 | to sign your email, but you're encouraged to create and start | |
a457755c AC |
56 | using a PGP key. See also: |
57 | <https://www.gnupg.org/faq/gnupg-faq.html#use_pgpmime> | |
3c378b9e AC |
58 | |
59 | There are many ways you can sign your patches, and it depends on | |
bd7badfd AC |
60 | your preferred tools. You can use neomutt(1) (>= 20240201) as a |
61 | driver for git-send-email(1). In <~/.gitconfig>, add the | |
62 | following section: | |
3c378b9e AC |
63 | |
64 | [sendemail] | |
bd7badfd | 65 | sendmailcmd = neomutt -C -H - && true |
3c378b9e | 66 | |
c93e2eec | 67 | See also |
3e7901ff | 68 | CONTRIBUTING.d/bugs |
ebc51bed | 69 | CONTRIBUTING.d/external_pages |
89cd7d9c | 70 | CONTRIBUTING.d/lint |
beb01a3c | 71 | CONTRIBUTING.d/patches |
42fa24a2 | 72 | CONTRIBUTING.d/style |
974845c5 | 73 | |
c93e2eec | 74 | <https://www.kernel.org/doc/man-pages/linux-man-ml.html> |
c93e2eec AC |
75 | <https://www.kernel.org/doc/man-pages/missing_pages.html> |
76 | <https://www.kernel.org/doc/man-pages/code_of_conduct.html> |