Dustin Sallings <dustin <at> spy.net> writes:
> strip (part of mq) will remove the branch if you give it the
> changeset ID of the first changeset of the branch.
>
> If you could give it a branch name, it'd basically do what you want
> without having to think about it. It doesn't take a branch name now,
> so you'd have to manually track down the first branched changeset.
>
> Do keep in mind, though, that any ancestry will be killed off. If
> you merged that branch in, strip will remove that merge, and any
> children of that merge. It will definitely remove any evidence that
> you've done that work.
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).
-- Pazu
_______________________________________________
Mercurial mailing list
Mercurial@...
http://selenic.com/mailman/listinfo/mercurial
