binutils doc update

Here's another small patch to lay the groundwork for the git
conversion.  This one updates the BFD and binutils documentation for
the move.

bfd:
	* doc/bfdint.texi (BFD generated files): Mention git, not cvs.
binutils:
	* MAINTAINERS: Mention git, not cvs.
	* README: Mention git, not cvs.

bfd/doc/bfdint.texi

@@ -1,6 +1,6 @@
 \input texinfo
 @c Copyright 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998,
-@c 2000, 2001, 2002, 2003, 2004, 2006, 2007, 2009
+@c 2000, 2001, 2002, 2003, 2004, 2006, 2007, 2009, 2013
 @c Free Software Foundation, Inc.
 @setfilename bfdint.info
 
@@ -945,7 +945,7 @@ BFD.  Some files are automatically rebuilt at make time, but only if
 you configure with the @samp{--enable-maintainer-mode} option.  Some
 files live in the object directory---the directory from which you run
 configure---and some live in the source directory.  All files that live
-in the source directory are checked into the CVS repository.
+in the source directory are checked into the git repository.
 
 @table @file
 @item bfd.h

binutils/MAINTAINERS

@@ -252,20 +252,20 @@ would be appropriate if the branch was created on January 1st, 2005.
 
 Having selected the branch name, create the branch as follows:
 
-1. Check out binutils, so that you have a CVS checkout corresponding
+1. Check out binutils, so that you have a git checkout corresponding
    to the initial state of your branch.
 
 2. Create a tag:
 
-     cvs tag binutils-<org>-<name>-branchpoint
+     git tag binutils-<org>-<name>-branchpoint
 
    That tag will allow you, and others, to easily determine what's
    changed on the branch relative to the initial state.
 
-3. Create the branch:
+3. Create and push the branch:
 
-     cvs rtag -b -r binutils-<org>-<name>-branchpoint \
-       binutils-<org>-<name>-branch
+     git checkout -b binutils-<org>-<name>-branch
+     git push origin HEAD
 
 4. Document the branch:
 

binutils/README

@@ -170,7 +170,7 @@ Always mention the version number you are running; this is printed by
 running any of the binutils with the --version option.  We appreciate
 reports about bugs, but we do not promise to fix them, particularly so
 when the bug report is against an old version.  If you are able, please
-consider building the latest tools from CVS to check that your bug has
+consider building the latest tools from git to check that your bug has
 not already been fixed.
 
 When reporting problems about gas and ld, it's useful to provide a