[gnus git] branch master updated: m0-11-65-gd13cc85 =1= texi/gnus-coding.texi: Neutralized language specific to a repository type

       via  d13cc85196efd6a50169b28c82fe75d64bc8aa3d (commit)
      from  dea42ba9a9f0bb6c660773ceddc3542b105ee9f9 (commit)


- Log -----------------------------------------------------------------
commit d13cc85196efd6a50169b28c82fe75d64bc8aa3d
Author: Eric S. Raymond <[email protected]>
Date:   Sun Oct 26 13:00:31 2014 +0000

    texi/gnus-coding.texi: Neutralized language specific to a repository type

diff --git a/texi/ChangeLog b/texi/ChangeLog
index 168637a..7a38f5b 100644
--- a/texi/ChangeLog
+++ b/texi/ChangeLog
@@ -1,3 +1,7 @@
+2014-10-25  Eric S. Raymond  <[email protected]>
+
+	* gnus-coding.texi: Neutralized language specific to a repository type.
+
 2014-07-31  Tassilo Horn  <[email protected]>
 
 	* gnus.texi (Group Parameters): Document that `gcc-self' may also be a
diff --git a/texi/gnus-coding.texi b/texi/gnus-coding.texi
index 0b2b063..adbdd68 100644
--- a/texi/gnus-coding.texi
+++ b/texi/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.
 

-----------------------------------------------------------------------
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we listed those
revisions in full, above.

Summary of changes:
 texi/ChangeLog        |    4 ++++
 texi/gnus-coding.texi |   14 +++++++-------
 2 files changed, 11 insertions(+), 7 deletions(-)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Gnus Project".

The branch, master has been updated


hooks/post-receive
-- 
Gnus Project