* notes/elpa: Use "git" instead of "bzr" in the name of machine to

clone the repository from.

diff --git a/admin/ChangeLog b/admin/ChangeLog
index 71f936865c59da93bc93d07667b6393b7f46b66b..907068e7f3c607f55a5a62fea3da0fad2e4168b7 100644 (file)
--- a/admin/ChangeLog
+++ b/admin/ChangeLog
@@ -1,3 +1,8 @@
+2014-06-16  Stephen Berman  <Stephen.Berman@gmx.net>
+
+       * notes/elpa: Use "git" instead of "bzr" in the name of machine to
+       clone the repository from.
+
 2014-05-26  Paul Eggert  <eggert@cs.ucla.edu>
 
        Include sources used to create macuvs.h.

diff --git a/admin/notes/elpa b/admin/notes/elpa
index 469a0ca8bd195624086351c84d12ef0c3d209de8..39226044a918c702aec8fe01ac872c4fdfe6b99b 100644 (file)
--- a/admin/notes/elpa
+++ b/admin/notes/elpa
@@ -3,9 +3,9 @@ NOTES ON THE EMACS PACKAGE ARCHIVE
 The GNU Emacs package archive, at elpa.gnu.org, is managed using a Git
 repository named "elpa", hosted on Savannah.  To check it out:
 
-  git clone git://bzr.sv.gnu.org/emacs/elpa
+  git clone git://git.sv.gnu.org/emacs/elpa
   cd elpa
-  git remote set-url --push origin git+ssh://bzr.sv.gnu.org/srv/git/emacs/elpa
+  git remote set-url --push origin git+ssh://git.sv.gnu.org/srv/git/emacs/elpa
   [create task branch for edits, etc.]
 
 Changes to this branch propagate to elpa.gnu.org via a "deployment" script run