Re: Need help for a hg push
* Michael Sperber <sperber(a)deinprogramm.de>:
Hello Mike,
Norbert, there's something really strange about your workflow.
:-)
I have trouble understanding because I don't know what exactly
you
did, and what "uploaded" and "new set" mean.
I was talking about the newly pre-released packages.
> nk＠vserv:test% hg st -qS
> M xemacs-packages/Sun/.hgtags
> [...]
> because these changes have been committed locally.
And what does "these changes" mean?
These changes I refer to are mine, and I simply haven't realized (up to
now) that I have to commit changes to local packages in the top-level
xemacs-package hierarchy as well. At least this is how I understand the
rest of your message. Please correct me, if I'm wrong.
I had the opinion it sufficient to either commit in the local package
*or* in the top-level package hierarchy.
IMHO, what you should do is very simple, depending on the situation:
1. Somebody makes a change to a package and you want to include that in
the global xemacs-packages hierarchy.
You do:
cd xemacs-packages/<package>
hg pull -u
cd ../..
hg commit -m "Update package X."
2. You want to update a package:
cd xemacs-packages/<package>
... edit ...
hg commit -m "<log message>"
2.1 You then want to include that update in the global xemacs-packages
hierarchy:
cd ../..
hg commit -m "Update package X."
3. You want to update something in xemacs-packages itself
... edit ...
hg commit -m "<log message>"
Does that help at all? How did your procedure differ?
See above. I haven't committed in the top-level hierarchy.
If this is the way I have to twiddle with Mercurial sub repos, yes, very
much.
The only thing missing now are the pushes. Do I push locally in the
package and on top-level or is the latter sufficient?
Thanks,
norbert.
--
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta