Backport changes in preparation for git migration from trunk.

 admin: Changes in several documents.
 autogen.sh: Neutralize language specific to a repository type.

 doc/misc/efaq-w32.texi: Neutralized language specific to a repository type.

 doc/misc/gnus-coding.txt: Neutralized language specific to a repository type.

 lisp/Makefile.in: Change some production names so they're neutral
 about the repository type.

4 files changed, 18 insertions, 14 deletions

diff --git a/doc/misc/ChangeLog b/doc/misc/ChangeLog
index e4a7e1f93ce..a9a5550a85e 100644
--- a/doc/misc/ChangeLog
+++ b/doc/misc/ChangeLog
@@ -1,3 +1,9 @@
+2014-10-31  Eric S. Raymond  <esr@thyrsus.com>
+
+        * efaq-w32.texi: Neutralized language specific to a repository type.
+
+        * gnus-coding.txt: Neutralized language specific to a repository type.
+
 2014-10-30  Glenn Morris  <rgm@gnu.org>
 
         * efaq.texi (Gnus does not work with NNTP): Remove; ancient.
diff --git a/doc/misc/efaq-w32.texi b/doc/misc/efaq-w32.texi
index c59f7547d8d..13627eb6b69 100644
--- a/doc/misc/efaq-w32.texi
+++ b/doc/misc/efaq-w32.texi
@@ -176,7 +176,7 @@ The latest source is available from
 distributed as a compressed tar file, digitally signed by the maintainer
 who made the release.
 
-@cindex Bzr, getting Emacs
+@cindex getting Emacs
 @cindex latest development version of Emacs
 @cindex Emacs Development
 The development version of Emacs is available from
@@ -199,8 +199,8 @@ of GNU @command{rm} and @command{cp}, as the Windows native
 equivalents are not consistent between versions.  GNU texinfo will be
 required to build the manuals.  @xref{Other useful ports}.
 
-After unpacking the source, or checking out of Bzr, be sure to read the
-instructions in @file{nt/README} and @file{nt/INSTALL}.
+After unpacking the source, or checking out of the repository, be sure
+to read the instructions in @file{nt/README} and @file{nt/INSTALL}.
 
 @node Debugging
 @section How do I use a debugger on Emacs?
diff --git a/doc/misc/efaq.texi b/doc/misc/efaq.texi
index 9c9b5a770a9..89f277be492 100644
--- a/doc/misc/efaq.texi
+++ b/doc/misc/efaq.texi
@@ -986,10 +986,8 @@ version; three components indicate a development
 version (e.g., @samp{23.0.50} is what will eventually become @samp{23.1}).
 
 Emacs is under active development, hosted at
-@uref{http://savannah.gnu.org/projects/emacs/, Savannah}.  The source
-code can be retrieved anonymously following the
-@uref{http://savannah.gnu.org/bzr/?group=emacs, instructions}.
-The repository is GNU Bazaar.
+@uref{http://savannah.gnu.org/projects/emacs/, Savannah}.
+Follow the instructions given there to clone the project repository.
 
 Because Emacs undergoes many changes before a release, the version
 number of a development version is not especially meaningful.  It is
diff --git a/doc/misc/gnus-coding.texi b/doc/misc/gnus-coding.texi
index 44cc29b9c39..e955b14e2ac 100644
--- a/doc/misc/gnus-coding.texi
+++ b/doc/misc/gnus-coding.texi
@@ -313,17 +313,17 @@ If it's a file which is thought of as being outside of Gnus (e.g., the
 new @file{encrypt.el}), you should probably make the change in the Emacs
 tree, and it will show up in the Gnus tree a few days later.
 
-If you don't have Emacs bzr access (or it's inconvenient), you can
-change such a file in the v5-10 branch, and it should propagate to Emacs
-bzr---however, it will get some extra scrutiny (by Miles) to see if the
-changes are possibly controversial and need discussion on the mailing
-list.  Many changes are obvious bug-fixes however, so often there won't
-be any problem.
+If you don't have Emacs repository access (or it's inconvenient), you
+can change such a file in the v5-10 branch, and it should propagate to
+the Emacs repository---however, it will get some extra scrutiny (by
+Miles) to see if the changes are possibly controversial and need
+discussion on the mailing list.  Many changes are obvious bug-fixes
+however, so often there won't be any problem.
 
 @item
 If it's to a Gnus file, and it's important enough that it should be part
 of Emacs and the v5-10 branch, then you can make the change on the v5-10
-branch, and it will go into Emacs bzr and the Gnus git trunk (a few days
+branch, and it will go into Emacs and the Gnus git trunk (a few days
 later).  The most prominent examples for such changes are bug-fixed
 including improvements on the documentation.