PR symtab/17559

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

diff --git a/gdb/CONTRIBUTE b/gdb/CONTRIBUTE
index 04d1568859afccc4eba1c744c41632f8078a8fa5..30f51ccdc7fb3ebe50beed27eb17af1ca5180523 100644 (file)
--- a/gdb/CONTRIBUTE
+++ b/gdb/CONTRIBUTE
@@ -32,11 +32,12 @@ o   Coding Standards
        Submissions which do not conform to the standards will be
        returned with a request to reformat the changes.
 
+       Ref: http://www.gnu.org/prep/standards_toc.html
+
        GDB has certain additional coding requirements.  Those
-       requirements are explained in the GDB internals documentation
-       in the gdb/doc directory.
+       requirements are explained in the GDB internals documentation.
 
-       Ref: http://www.gnu.org/prep/standards_toc.html
+       Ref: http://sourceware.org/gdb/wiki/Internals%20Coding-Standards
 
 
 o      Copyright Assignment
@@ -49,7 +50,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
 
@@ -69,21 +71,21 @@ o   Submitting Patches
        unlike some other projects, we do require ChangeLogs also for
        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
-       "diff -up OLD NEW". If your version of diff does not support
-       these options, then get the latest version of GNU diff.
+       The patch itself.  If you are accessing the git repository, use
+       "git diff", remembering first to update to the current master;
+       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),
        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
-       Read-write CVS access page.
+       git repository, see the Anonymous read-only git access and
+       Read-write git access page.
 
 --
 
@@ -115,19 +117,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
@@ -139,5 +141,5 @@ o   When submitting a patch that fixes a bug
        Fix PR gdb/4705.
 
        The text ``PR gdb/4705'' should also be included
-       in the CVS commit message.  That causes the
+       in the git commit message.  That causes the
        patch to automatically be archived with the PR.