obscolescence markers are rebase without losing any history?

Simon King simon at simonking.org.uk
Tue Aug 19 11:43:22 UTC 2014


On Tue, Aug 19, 2014 at 11:02 AM, anatoly techtonik <techtonik at gmail.com> wrote:
> Hi,
>
> Do obsolescence markers on server side allow rebasing
> named branches without losing history?
>
> If there is a second repository with commits on top of
> named branch, will these commit automatically move to
> a top of rebased named branch after the pull?
>

I don't think anything will happen automatically. After the rebased
changes are pulled into the second repository, the commits on top of
the old branch will be considered unstable and you'll need to call "hg
stabilize" to rebase them:

http://hg-lab.logilab.org/doc/mutable-history/html/tutorials/tutorial.html#rebasing-unstable-change-after-pull

Simon



More information about the Mercurial mailing list