added Adrian's comments

1 files changed, 21 insertions, 15 deletions

diff --git a/HOWTO b/HOWTO
index ede78595c1a56d..ddb6e781b6aaae 100644
--- a/HOWTO
+++ b/HOWTO
@@ -29,7 +29,6 @@ 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]
  - "Programming the 80386" by Crawford and Gelsinger [Sybex]
- - "UNIX Systems for Modern Architectures" by Curt Schimmel [Addison Wesley]
 
 The kernel is written using GNU C and the GNU toolchain.  While it
 adheres to the ISO C89 standard, it uses a number of extensions that are
@@ -43,13 +42,13 @@ definitive reference for them.  Please check the gcc info pages (`info
 gcc`) for some information on them.
 
 Please remember that you are trying to learn how to work with the
-existing development community.  It is a very diverse group of people,
-with very high standards for coding, style and procedure.  These
-standards 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 standards ahead of time, as they
-are well documented; do not expect people to adapt to you or your
-company's way of doing things.
+existing development community.  It is a diverse group of people, with
+high standards for coding, style and procedure.  These standards 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 standards ahead of time, as they are well
+documented; do not expect people to adapt to you or your company's way
+of doing things.
 
 
 Legal Issues
@@ -62,6 +61,9 @@ contact a lawyer, and do not ask on the Linux kernel mailing list.  The
 people on the mailing lists are not lawyers, and you should not rely on
 their statements on legal matters.
 
+For common questions and answers about the GPL, please see:
+	http://www.gnu.org/licenses/gpl-faq.html
+
 
 Documentation
 ------------
@@ -357,7 +359,8 @@ Bug Reporting
 
 bugzilla.kernel.org is where the Linux kernel developers track kernel
 bugs.  Users are encouraged to report all bugs that they find in this
-tool.
+tool.  For details on how to use the kernel bugzilla, please see:
+	http://test.kernel.org/bugzilla/faq.html
 
 The file REPORTING-BUGS in the main kernel source directory has a good
 template for how to report a possible kernel bug, and details what kind
@@ -450,6 +453,12 @@ the kernel.  Or at least be willing to prove your idea is worth it.
 Remember, being wrong is acceptable as long as you are willing to work
 toward a solution that is right.
 
+It is normal that the answers to your first patch might simply be a list
+of a dozen things you should correct.  This does _not_ imply that your
+patch will not be accepted, and it is _not_ meant against you
+personally.  Simply correct all issues raised against your patch and
+resend it.
+
 
 Differences between the kernel community and corporate structures
 -----------------------------------------------------------------
@@ -469,7 +478,6 @@ do to try to avoid problems:
     - "We did it this way in AIX/ptx/Solaris, so therefore it must be
       good..."
     - "I've being doing this for 20 years, so..."
-    - "It makes this proprietary benchmark go faster"
     - "This is required for my company to make money"
     - "This is for our Enterprise product line."
     - "Here is my 1000 page design document that describes my idea"
@@ -487,9 +495,7 @@ because all you are is an email address.  The international aspect also
 helps to level the playing field because you can't guess gender based on
 a person's name. A man may be named Andrea and a woman may be named Pat.
 Most women who have worked in the Linux kernel and have expressed an
-opinion have had positive experiences.  Here is a group that is a good
-starting point for women interested in contributing to Linux:
-	http://www.linuxchix.org/
+opinion have had positive experiences.
 
 The language barrier can cause problems for some people who are not
 comfortable with English.  A good grasp of the language can be needed in
@@ -596,8 +602,8 @@ to be based on text he had written, and to Randy Dunlap and Gerrit
 Huizenga for some of the list of things you should and should not say.
 Also thanks to Pat Mochel, Hanna Linder, Randy Dunlap, Kay Sievers,
 Vojtech Pavlik, Jan Kara, Josh Boyer, Kees Cook, Andrew Morton, Andi
-Kleen, Vadim Lobanov, Jesper Juhl, and Alex Shepard for their review and
-comments on early drafts of this document.
+Kleen, Vadim Lobanov, Jesper Juhl, Adrian Bunk, and Alex Shepard for
+their review and comments on early drafts of this document.