Pazu <
pazu@...> writes:
> Reviving an old thread: what if I don't want to lose any ancestry, or
> really delete any commits -- I just want to get rid of the _name_.
> This way I can work on multiple (potentially short lived) named
> branches without polluting the namespace on a long term.
>
> I know the standard answer for this is "use multiple repositories",
> but I was wondering if I could somehow accomodate this in a single
> repository. Setting up a new remote repository every couple days isn't
> my idea of fun, considering the work that goes into it (compared to
> named branches, anyway).
I have only tried it very briefly, but the LocalBranches extension (if
it still works with Mercurial 1.0) might be what you are looking for. It
allows you to work with branches that exist in your repository only.
http://www.selenic.com/mercurial/wiki/index.cgi/LocalbranchExtension--
Martin Geisler
VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multi-Party Computation) to Python. See:
http://viff.dk/.
_______________________________________________
Mercurial mailing list
Mercurial@...
http://selenic.com/mailman/listinfo/mercurial