daily update

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

diff --git a/gdb/CONTRIBUTE b/gdb/CONTRIBUTE
index 04d1568859afccc4eba1c744c41632f8078a8fa5..2d24bba2ec629e5a208a3c0231c75eb5a9ea4b80 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,7 +71,7 @@ o     Submitting Patches
        documentation (i.e., .texi files).
 
        The patch itself. If you are accessing the CVS repository use
-       "cvs update; cvs diff -c3p"; else, use "diff -c3p OLD NEW" or
+       "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.
 
@@ -79,7 +80,7 @@ o     Submitting Patches
        or as uuencoded gzipped text.
 
        When you have all these pieces, bundle them up in a mail
-       message and send it to gdb-patches@sources.redhat.com. All
+       message and send it to gdb-patches@sourceware.org. All
        patches and related discussion should be sent to the
        gdb-patches mailinglist. For further information on the GDB
        CVS repository, see the Anonymous read-only CVS access and
@@ -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