X-Git-Url: http://cgit.sxemacs.org/?a=blobdiff_plain;f=texi%2Fgnus-coding.texi;h=adbdd689b448d14045a9d43aebef807783d01976;hb=d13cc85196efd6a50169b28c82fe75d64bc8aa3d;hp=2ce9d71788e16a0b1041586a397306753653fdaa;hpb=b4bc300f0dcddc2b17bb50a3501ed6e6db1ef12c;p=gnus

diff --git a/texi/gnus-coding.texi b/texi/gnus-coding.texi
index 2ce9d7178..adbdd689b 100644
--- a/texi/gnus-coding.texi
+++ b/texi/gnus-coding.texi
@@ -1,7 +1,8 @@
 \input texinfo
 
-@setfilename gnus-coding
+@setfilename gnus-coding.info
 @settitle Gnus Coding Style and Maintenance Guide
+@documentencoding UTF-8
 @syncodeindex fn cp
 @syncodeindex vr cp
 @syncodeindex pg cp
@@ -14,7 +15,7 @@ Foundation, Inc.
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the GNU Free Documentation License, Version 1.3 or
 any later version published by the Free Software Foundation; with no
-Invariant Sections, with the Front-Cover texts being ``A GNU Manual'',
+Invariant Sections, with the Front-Cover Texts being ``A GNU Manual'',
 and with the Back-Cover Texts as in (a) below.  A copy of the license
 is included in the section entitled ``GNU Free Documentation License''.
 
@@ -312,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.