Remove ui_out_destroy

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

diff --git a/gdb/CONTRIBUTE b/gdb/CONTRIBUTE
index 75b6ddf509cfffad1e028c3cfb1d85fed72c24fc..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.
 
        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
        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
 
 
 o      Copyright Assignment


@@ -70,10 +71,10 @@ o   Submitting Patches
        unlike some other projects, we do require ChangeLogs also for
        documentation (i.e., .texi files).
 
        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 -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.
+       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),
 
        We accept patches as plain text (preferred for the compilers
        themselves), MIME attachments (preferred for the web pages),


@@ -83,8 +84,8 @@ o     Submitting Patches
        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
        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.

 
 --
 
 
 --
 


@@ -121,7 +122,7 @@ o   If ``gdb/configure.ac'' is modified then you don't
        ``configure''.
 
        The maintainer will re-generate those files
        ``configure''.
 
        The maintainer will re-generate those files

-       using autoconf (2.59 as of 2005-01-07).
+       using autoconf (2.64 as of 2009-08-22).

 
 
 o      If ``gdb/gdbarch.sh'' is modified, you don't
 
 
 o      If ``gdb/gdbarch.sh'' is modified, you don't


@@ -140,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
        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.
        patch to automatically be archived with the PR.