xemacsweb / Releases / patchProb.content

john s jacobs anderson reposting content from c.e.xemacs
Patch List troubles (8/22/1999)

  <h1>Some XEmacs Patch List troubles</h1>

  <p>The following was posted to comp.emacs.xemacs on 22 August 1999:</p>

  <pre xml:space="preserve">
Date: Sun, 22 Aug 1999 21:07:31 +0200
From: (XEmacs Team)
Subject: XEmacs-Patches list problems
Newsgroups: comp.emacs.xemacs

To all people who have send patches to the XEmacs Patches list and
have not had feedback.

The list is the entry point for all
contributions to the XEmacs source and/or packages. It is "moderated"
by a bot that checks whether the messages actually contains a patch.
The normal procedure after send a patch to this address is as follows:

1. Immediately you will get a message from the bot confirming the
   receipt of the patch.
2. The patch is archived at
3. Either
       3.a.1 You will receive a message that your patch has been
             Checked & Approved for inclusion, followed by
       3.a.2 A message confirming the patch has been applied to the
       3.b. A message telling you the patch has been rejected and why
            (normally with suggestions for improvement).

However, it has been discovered that the bot had a configuration error
that dropped some patches on the floor after sending out the automated
confirmation messages. This problem as how been rectified. If you have 
send a patch to and hear nothing except for
the automated replay then please do so again.

We apologize for the inconvenience. Please be advised, however, that
we are not able to give refunds.

P.S. Now what I have your attention, let me point out that the ideal
patch contains
  - A short description of the problem solved.
  - A ChangeLog entry (c.f M-x add-change-log-entry) included
    literally (not as a diff).
  - A unified diff (diff -u) of the changed file, made from the
    toplevel XEmacs directory.
This greatly simplifies the jobs of the patch reviewers and appliers.

  <br /><br />

  <!-- Keep this comment at the end of the file
  Local variables:
  mode: xml
  sgml-parent-document:("../template.html" "html" "body" "table" "tr" "td")