Re: Need help for a hg push
Stephen J. Turnbull wrote:
7. hg commit. (This should update the subrepos, see below.) I
think
you should be able to check with "hg diff -S" in the top directory.
8. Tag (I don't think we do this now, but I wonder if it's not a good
idea).
9. Make new packages and upload them. Announce availability.
There should be another push to bitbucket somewhere in there, I think.
After step 8?
There may be other workflows that work, but I suspect that we really
don't want anybody but Norbert committing in the top, xemacs-packages,
and mule-packages directories.
When I (someday) get the mh-e package updated, I'll be wanting to change
package-compile.el to reflect moving the sources from mh-e/ to
mh-e/lisp/. I suppose that changes like this won't happen very often,
so they can be managed by submitting patches to Norbert (or whoever is
the package builder). Does this sound okay?
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta