summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Tromey <tromey@redhat.com>2013-09-17 09:18:52 -0600
committerTom Tromey <tromey@sourceware.org>2013-10-25 14:02:58 +0000
commit279d4c119955638dc0649c34971ff50f68959587 (patch)
tree6b40c2a4417ef9e507825c4531d769c910aab801
parent95e4302a8f872b3f68c4cf5af774ca1bde9d2c1a (diff)
downloadbinutils-gdb-279d4c119955638dc0649c34971ff50f68959587.tar.gz
fix CONTRIBUTE for git migration
This fixes gdb's CONTRIBUTE file for the git migration. * CONTRIBUTE: Update for git.
-rw-r--r--gdb/CONTRIBUTE14
1 files changed, 7 insertions, 7 deletions
diff --git a/gdb/CONTRIBUTE b/gdb/CONTRIBUTE
index cdec2464b91..03f21611a2c 100644
--- a/gdb/CONTRIBUTE
+++ b/gdb/CONTRIBUTE
@@ -70,10 +70,10 @@ 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 -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),
@@ -83,8 +83,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
- 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.
--
@@ -140,5 +140,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.