[Emacs-diffs] trunk r118208: Neutralize language specific to a repository type.

[Eric S. Raymond]

------------------------------------------------------------
revno: 118208
revision-id: address@hidden
parent: address@hidden
committer: Eric S. Raymond <address@hidden>
branch nick: trunk
timestamp: Sat 2014-10-25 15:23:20 -0400
message:
  Neutralize language specific to a repository type.
modified:
  doc/misc/ChangeLog             changelog-20091113204419-o5vbwnq5f7feedwu-6331
  doc/misc/gnus-coding.texi      
gnuscoding.texi-20091113204419-o5vbwnq5f7feedwu-7530

=== modified file 'doc/misc/ChangeLog'
--- a/doc/misc/ChangeLog        2014-10-21 01:17:06 +0000
+++ b/doc/misc/ChangeLog        2014-10-25 19:23:20 +0000
@@ -1,3 +1,7 @@
+2014-10-25  Eric S. Raymond  <address@hidden>
+
+       * gnus-coding.txt: Neutralized language specific to a repository type.
+
 2014-10-20  Glenn Morris  <address@hidden>
 
        * Merge in all changes up to 24.4 release.

=== modified file 'doc/misc/gnus-coding.texi'
--- a/doc/misc/gnus-coding.texi 2014-06-10 02:20:31 +0000
+++ b/doc/misc/gnus-coding.texi 2014-10-25 19:23:20 +0000
@@ -313,17 +313,17 @@
 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.