2009/7/18 Hanno Schlichting <[email protected]>: > I don't see the problem. Note that branches in Mercurial are quite > different from branches in SVN. Also typical SVN-style use might not > be appropriate for Mercurial. I'm myself using this only for a very > short time, so I'm in no position to lecture people about anything > here. > > But looking at http://bitbucket.org/tarek/distribute/changesets/ all > looks fine to me. I gave the setuptools-0.6 branch the name default > now, which seems to cause it to be the "default" you get as a working > copy when cloning the repo.
OK, that solved that problem. It's annoying that you can't delete branches so they won't show up. OK, you can inactivate them, but the default is to list all, and you have to type --active to not list the inactive ones. That's just daft. It means that if you make a mistake, like I did, you have to basically live with that mistake, and you can't prune old branches in any reasonable way. In svn, if you delete a branch it's gone. Except in history, so they still exist if you look at the correct revision. That's the reasonable way to do things. Indeed, branches is very different from svn. But it cloning the right way? What happens when you want to merge from different clones? And can you have named clones? Anyway. I found that with the mqextension strip you seem to be able to delete branches. I'd be happy to delete all my changes this way, and start over, this seems doable. (It's not much work). But before I do this, I would like confirmation that I should do this. I think it's a good idea. The python3 branch is broken now anyway. Thanks for helping out with this, Hanno. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
