Mercurial > emacs
view admin/notes/BRANCH @ 103352:827a8db0b5ad
Synch with Gnus trunk:
2009-06-01 Katsumi Yamaoka <yamaoka@jpl.org>
* gnus-art.el (gnus-mime-delete-part): Specify gnus-decoded as charset
to deleted part.
2009-05-30 David Engster <dengste@eml.cc>
* nnmairix.el: Remove old documentation in the commentary block.
(nnmairix-request-group): Do not update active file for nnml back ends.
(nnmairix-retrieve-headers): Set gnus-nov-is-evil to t for nnimap back
end so that overview files are ignored.
(nnmairix-update-groups): Make updating the groups more robust by using
marks.
(nnmairix-determine-original-group-from-path): Circumvent mairix bug
with dollar characters in message-id.
| author | Katsumi Yamaoka <yamaoka@jpl.org> |
|---|---|
| date | Mon, 08 Jun 2009 22:47:11 +0000 |
| parents | 8080c98e919f |
| children | bd5f6908042c |
line wrap: on
line source
This file describes the CVS branch in which it is maintained. Everything below the line is branch-specific. ________________________________________________________________________ This is the trunk (sometimes mistakenly called "HEAD"). When people say "use CVS emacs", this is the branch they are talking about. Likewise, a "cvs checkout" without the "-r" option results in this branch. Emacs development takes place on the trunk. Most of the time, Emacs hackers add to it relatively free of constraint (aside from proper legal / accounting practices), although sometimes there is related discussion on the emacs-devel mailing list. Sometime before the release of a new major version of Emacs (eg 22.1), a "feature freeze" is imposed on the trunk. No new features may be added after this point. This is usually many months before the release. During this time, there is no official place for development of new features. Shortly before the release, a release branch is created. For example, EMACS_22_BASE or EMACS_21_1_RC for Emacs 22.x and 21.x, respectively. (Unfortunately the naming scheme has not always been consistent.) The release branch is used to make the release (22.1), and all later members of the series (22.2, 22.3, etc). Generally, only bug-fixes have been allowed in the minor releases, although in 22.x, self-contained new features were allowed on a case-by-case basis. From the point that a release branch is created, the trunk is free for development for the next major version.