GDB 7.6.50

gdb/CONTRIBUTE

 
                         Contributing to GDB
 
 GDB is a collaborative project and one which wants to encourage new
 development.  You may wish to fix GDB bugs, improve testing, port GDB
 to a new platform, update documentation, add new GDB features, and the
 like. To help with this, there is a lot of documentation
 available.. In addition to the user guide and internals manual
 included in the GDB distribution, the GDB web pages also contain much
 information.
@@ skipping 52 matching lines @@
         A description of the bug and how your patch fixes this
         bug. A reference to a testsuite failure is very helpful. For
         new features a description of the feature and your
         implementation.
 
         A ChangeLog entry as plaintext (separate from the patch); see
         the various ChangeLog files for format and content. Note that,
         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 -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.
+        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@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.
 
 --
 
 Supplemental information for GDB:
 
 o       Please try to run the relevant testsuite before and after
         committing a patch
 
         If the contributor doesn't do it then the maintainer will.  A
         contributor might include before/after test results in their
@@ skipping 35 matching lines @@
 
 o       When submitting a patch that fixes a bug
         in GDB's bug database a brief reference
         to the bug can be included in the ChangeLog
         vis
 
         * CONTRIBUTE: Mention PR convention.
         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.