diff options
author | Kees Cook <kees@outflux.net> | 2005-11-14 15:58:04 -0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@suse.de> | 2005-11-14 20:41:45 -0800 |
commit | 77044c1afe11e301713f8bef87dee15bb01c472e (patch) | |
tree | 32e574f9ed7d5f684b6bfd01266f2447667c5bb1 /HOWTO | |
parent | b72dae79b49d98572425b9249c292892222e6079 (diff) | |
download | patches-77044c1afe11e301713f8bef87dee15bb01c472e.tar.gz |
[PATCH] HOWTO
Saw a few typos, added a gmane.org link for lkml searching:
Diffstat (limited to 'HOWTO')
-rw-r--r-- | HOWTO | 18 |
1 files changed, 10 insertions, 8 deletions
@@ -21,11 +21,11 @@ and hints on how to work with the community. It will also try to explain some of the reasons why the community works like it does. The kernel is written mostly in C, with some architectural-dependent -parts written in assembly. A good understanding of C is required to +parts written in assembly. A good understanding of C is required for kernel development. Assembly (any architecture) is not required unless you plan to do low-level development for that architecture. Though they are not a good substitute for a solid C education and/or years of -experience, the following books are good, if anything for reference: +experience, the following books are good for, if anything, reference: "The C Programming Language" by Kernighan and Ritchie [Prentice Hall] "Practical C Programming" by Steve Oualline [O'Reilly] @@ -46,7 +46,7 @@ with very high standards for coding, style and procedure. These procedures have been created over time based on what they have found to work best for such a large and geographically dispersed team. Try to learn as much as possible about these procedures ahead of time, as they -are well documented, and not expect people to adapt to you, or your +are well documented, and do not expect people to adapt to you or your company's way of doing things. @@ -192,10 +192,12 @@ developers participate on the Linux Kernel Mailing list. Details on how to subscribe and unsubscribe from the list, can be found at: http://vger.kernel.org/vger-lists.html#linux-kernel There are archives of the mailing list on the web in many different -places. Use a search engine to find these archives. It is highly -recommended that you search the archives about the topic you want to bring -up, before you post it to the list. A lot of things are already discussed -in detail and are only recorded at the mailing list archives. +places. Use a search engine to find these archives. For example: + http://dir.gmane.org/gmane.linux.kernel +It is highly recommended that you search the archives about the topic +you want to bring up, before you post it to the list. A lot of things +are already discussed in detail and are only recorded at the mailing +list archives. Most of the individual kernel subsystems also have their own separate mailing list where they do their development efforts. See the @@ -213,7 +215,7 @@ interacting with the list (or any list): If multiple people respond to your mail, the CC: list of recipients may get pretty large. Don't remove anybody from the CC: list without a good -reason, or don't reply only to the list address. Get used to receive the +reason, or don't reply only to the list address. Get used to receiving the mail twice, one from the sender and the one from the list and don't try to tune that by adding fancy mail-headers, people will not like it. |