On Sun, Mar 13, 2011 at 8:25 PM, Nick Coghlan <ncogh...@gmail.com> wrote:
> 1. While the feature branches are active, is it correct that I can't > use a bare "hg push" any more, since I don't want to push the feature > branches to hg.python.org? Instead, I need to name all the branches I > want to push explicitly. More or less. If you only want to push the default branch, you could put [alias] pdef = push -r default in the .hg/hgrc as an alias. > 2. Once I'm done with the feature branch, I need to nuke it somehow > (e.g. by enabling the mq extension to gain access to "hg strip" > command) You may *want* to do that, but hg branch obsolete-branch; hg commit -m "I'm done" --close should also do the trick of getting it out of the way of most commands. > If those are both accurate, I may actually create a new subclone, > leaving the main local repository with only the changes I actually > want to push upstream. This is also a good way to work for many people, I think. I personally manage my not-ready-for-prime time code with mq, though. This should protect you from pushing code you're not ready to publish. (hg will tell you wideload:test/b 20:54$ hg push pushing to /private/tmp/test/a abort: source has mq patches applied if you try to push with patches applied to the workspace.) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
