Jerry James writes:
Oops. Shall I sing the "I'm Very Sorry" song?
Oh, I don't think you need to do that.
I think I got confused because I did a push in the subrepo on one
machine, then later when I did an "hg pull" on another machine, it
didn't find my changes.
Did you do the "hg pull" at top level, or in the subrepo, on the
second host? If the latter, AFAIK you *should* get the changes even
though the top-level pull shows no changes. At least, I got them.
That's correct behavior by design, but confusing from our point of
view. Subrepos are designed for the case where you *don't* have any
control over upstream, and need to *pin* the version of that repo to
protect yourself from upstream churn. I don't know what to say except
"Patience, Grasshopper. Norbert will get to it." I think this is
best for beta testers, as well as simpler for Norbert.
Note that if you want to be notified of changes in the subrepos, you
can subscribe to the RSS feed for the xemacs project, or for a
specific repo.
What's the process for creating a new subrepo, then, if we decide
to
add a package?
Mike probably knows better, but AFAIK:
Just push to hg://hg@hg.xemacs.prg/xemacs-packages/foo, and tell
Norbert. He adds xemacs-packages/foo to the xemacs-packages/.hgsub,
hg updates, and commits.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta