How to get patches expedited
Recent patches have been very difficult to apply, so here's an updated
set of guidelines about how to create patches.
1. Patches should be submitted to xemacs-patches(a)xemacs.org for
review. If they go any place else, they run the risk of being
lost.
2. There should be a clear and concise description attached (separate
from the ChangeLog entry if that is necessary) as to why this
patch should be applied to XEmacs. We appreciate user
contributions to XEmacs, but XEmacs is precious. Please justify
why it needs to be changed.
3. Patches to XEmacs Lisp libraries are exempt from all rules in
this document, except rule X. Either check them in directly as
per the CVS guidelines posted separately, or send them on to
xemacs-patches if you don't have update access to the CVS tree,
and email jareth(a)xemacs.org for update access to packages which
you own.
4. All patches should have attached appropriate ChangeLog entries.
Patches without appropriate ChangeLog entries will be deferred.
5. ChangeLog entries should be divided into cut & pastable text as
per ChangeLog file. Patches to ChangeLog files Just Plain Don't
Work. File names should be rooted as appropriate to the ChangeLog
file being updated. Patches with all ChangeLog entries rooted to
the top-level directory will be deferred.
6. Patches to groups of files should be rooted somewhere
appropriate. Patches to anything in the XEmacs core should be
rooted at the top-level XEmacs source directory. Patches to
XEmacs lisp packages can be rooted anywhere so long as they can be
applied with a single patch -pX command.
It is not my intention to flame anyone in particular. CVS pretty much
guarentees that shitty patches are generated. If you model your
patches after the ones I post, Hrvoje Niksic posts, and Andy Piper
posts, you will be O.K.
If you feel anything in this posting is out of line, please let me
know.