QUERY: commit: Merge.

[Stephen J. Turnbull]

Vin Shelton writes:
 > QUERY -
 > 
 > On Dec 20, 2007 5:35 AM, Stephen Turnbull
 > <unwelcome-guest at alioth.debian.org> wrote:
 > > changeset:   4341:5938003821ac8b2fbb12f38379fdcfb115cf79a9
 > > tag:         tip
 > > parent:      4340:2834fcbd1a92d5007166f938e9d0959010f3c12f
 > > parent:      4339:89954a8cc73d4c1ad96065fc9d0ae5866f021127
 > > user:        Stephen J. Turnbull <stephen at xemacs.org>
 > > date:        Thu Dec 20 02:34:02 2007 -0800
 > > files:
 > > description:
 > > Merge.
 > 
 > Stephen - what is this message?

Thank you for your support!

According to Mike this is a normal feature of Mercurial.  Over on
xemacs-beta I'm trying to convince him it is a BadThang[tm].  Your
posts will help.

  Is this a merge to your private
 > workspace?  I got confused into thinking you had promoted Jerry's
 > change to the XEmacs-beta repository, but that's not the case, right?
 > Please arrange not to send personal commit messages to the
 > xemacs-patches list, it confuses this programmer of very small brain.
 > 
 > On a separate (but perhaps related) topic, Michael - how do you
 > propose to track when you (or I or anyone) promote changesets from the
 > hg xemacs repository to the hg xemacs-beta repository?  Ideally a
 > follow-up message to the original PATCH/COMMIT message similar to what
 > I send for 21.4 patches should be sent, but if sending a non-followup
 > message is easier to automate, then lets do that.  Either way, there
 > needs to be some message sent to XEmacs-patches for each commit to the
 > hg xemacs-beta repository.
 > 
 > BTW, in retrospect, "xemacs" is a bad name for the repository, I think
 > "xemacs-experimental" or "xemacs-bleeding-edge" would be a more
 > accurate name.
 > 
 > Regards,
 >   Vin