[Emacs-diffs] master 3172a6a: * admin/notes/repo: Fix a few obsolete references to Bazaar

[Juanma Barranquero]

branch: master
commit 3172a6ac39d98383451e8b36cd33d291347fc93b
Author: Juanma Barranquero <address@hidden>
Commit: Juanma Barranquero <address@hidden>

    * admin/notes/repo: Fix a few obsolete references to Bazaar
---
 admin/notes/repo |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/admin/notes/repo b/admin/notes/repo
index b27a3f4..3ab3da7 100644
--- a/admin/notes/repo
+++ b/admin/notes/repo
@@ -41,8 +41,8 @@ preferable not to merge from master until you are done with 
the
 feature.  Unless you really need some change that was done on the
 master while you were developing on the branch, you don't really need
 those merges; just merge once, when you are done with the feature, and
-Bazaar will take care of the rest.  Bazaar is much better in this than
-CVS, so interim merges are unnecessary.
+Git will take care of the rest.  Git is much better in this than CVS,
+so interim merges are unnecessary.
 
 Or use shelves; or rebase; or do something else.  See the thread for
 yet another fun excursion into the exciting world of version control.