Need help for a hg push
sperber at deinprogramm.de
Sat Oct 22 08:02:53 EDT 2011
Norbert Koch <viteno at xemacs.org> writes:
> * Mike Kupfer <mike.kupfer at xemacs.org>:
>> 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?
> That's right, an interesting point.
> Should I push the local changes in the subrepo (e.g. ruby-modes like I
> just did) or should I push all my changes from the top-level?
It does not matter. I suggest pushing from the top level.
> After my push in ruby-modes, on the top-level I get
> % hg status --added --modified --subrepos
> M ChangeLog
> M xemacs-packages/ruby-modes/.hgtags
> M xemacs-packages/ruby-modes/ChangeLog
> M xemacs-packages/ruby-modes/Makefile
> I can discard the changes in the subrepo and try to merge/push, but that
> doesn't sound correct.
You mean the changes weren't there before?
> Another question arises. You said I should not update on top-level, but
> sometimes people check in changes in this directory. How do I get
> these? Or should I get patches and submit them myself?
Right now, hardly anybody except you can push to the top level.
> BTW, would it be easier - for now - to get the repository in state, to
> get a new clone?
There's certainly something strange going on with your setup, so that
might not be the worst idea.
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
More information about the XEmacs-Beta