procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Neutralize language specific to a repository type.

Browse source
This commit is contained in:
Eric S. Raymond 2014-10-25 15:23:20 -04:00
parent 5862e22c4a
commit 65e2cdadaf
2 changed files with 11 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/misc/ChangeLog
View file

@ -1,3 +1,7 @@
2014-10-25 Eric S. Raymond <esr@thyrsus.com>
* gnus-coding.txt: Neutralized language specific to a repository type.
2014-10-20 Glenn Morris <rgm@gnu.org>
* Merge in all changes up to 24.4 release.

14
doc/misc/gnus-coding.texi
View file

@ -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.