On Sat, May 10, 2014 at 1:45 AM, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
Jerry James writes:
> - Make changes needed for texinfo 5.x.
> - Restore CVS keyword expansions that were lost during the transition
> to mercurial.
Is this a good idea?
I think it mostly doesn't matter, but there are some cases where it
does, such as:
- mule-packages/skk/skk.el
- mule-packages/skk/texi/skk.texi
- mule-packages/mule-ucs/doc/mule-ucs.texi
- xemacs-packages/bbdb/lisp/bbdb.el
- xemacs-packages/bbdb/texinfo/bbdb.texinfo
- xemacs-packages/build/README
etc.
I don't see the harm in putting them all back versus picking through
to see which ones might actually matter.
You forgot
- Add button.el.
:-)
Apparently I don't understand how to use mercurial. I already did the
button.el change, committed it locally, and pushed. I then did this
patch in the same checked out package tree. Yet hg diff is showing
the button.el change as part of this patch. Is that because the
corresponding top-level change has not yet been made?
In any case, all the button.el-related stuff has already been done and pushed.
Here's another question. This new patch contains a top-level change,
.cvsignore -> .hgignore. I'm not supposed to do top-level pushes,
though, right? I messed things up the last time I did that. Or am I
just not supposed to do recursive top-level pushes? I don't
understand how this is supposed to work. If somebody could educate me
in advance, that would be great.
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Patches mailing list
XEmacs-Patches(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-patches