binutils

[deliverable/binutils-gdb.git] / gdb / CONTRIBUTE

diff --git a/gdb/CONTRIBUTE b/gdb/CONTRIBUTE
index f1f3cb05deea244515001c908fd8cdb622612a89..cdec2464b9173eb71e5c48ac2e2f09742ff29c49 100644 (file)
--- a/gdb/CONTRIBUTE
+++ b/gdb/CONTRIBUTE
@@ -49,7 +49,8 @@ o     Copyright Assignment
        taking care of your contributions) to obtain the relevant
        forms.
 
-       Small changes can be accepted without a copyright assignment form on file.
+        Small changes can be accepted without a copyright assignment form
+        on file.
 
        Ref: http://www.gnu.org/prep/maintain.html#SEC6
 
@@ -70,9 +71,9 @@ o     Submitting Patches
        documentation (i.e., .texi files).
 
        The patch itself. If you are accessing the CVS repository use
-       "cvs update; cvs diff -cp"; else, use "diff -cp OLD NEW" or
-       "diff -up OLD NEW". If your version of diff does not support
-       these options, then get the latest version of GNU diff.
+       "cvs update; cvs diff -up"; else, use "diff -up OLD NEW". If
+       your version of diff does not support these options, then get
+       the latest version of GNU diff.
 
        We accept patches as plain text (preferred for the compilers
        themselves), MIME attachments (preferred for the web pages),
@@ -115,19 +116,19 @@ o Please read your patch before submitting it.
        to re-formatting / split it.
 
 
-o      If ``gdb/configure.in'' is modified then you don't
+o      If ``gdb/configure.ac'' is modified then you don't
        need to include patches to the regenerated file
        ``configure''.
 
        The maintainer will re-generate those files
-       using autoconf (2.13 as of 2000-02-29).
+       using autoconf (2.64 as of 2009-08-22).
 
 
 o      If ``gdb/gdbarch.sh'' is modified, you don't
        need to include patches to the generated files
        ``gdbarch.h'' and ``gdbarch.c''.
 
-       See ``gdb/configure.in'' above.
+       See ``gdb/configure.ac'' above.
 
 
 o      When submitting a patch that fixes a bug