Pushing obsolescence markers
Xavier Zwirtz
me at xavierzwirtz.com
Sun Jul 10 00:07:23 UTC 2016
That looks like the exact same issue.
On 7/9/2016 4:56:26 PM, Faheem Mitha <faheem at faheem.info> wrote:
On Sat, 9 Jul 2016, Xavier Zwirtz wrote:
> In my experiments, hg push does as expected in almost all cases, ie it
> pushes obsolescence markers. It will not do that though, if the remote
> contains a a change to branch foo that client has marked obsolete, and
> you are trying to push a new branch at the same time. It does not detect
> that at the end of the transaction there will not be two heads.
This sounds similar to 4354. Is it the same bug or a different one?
https://bz.mercurial-scm.org/show_bug.cgi?id=4354
Regards, Faheem Mitha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20160709/98e3f047/attachment-0002.html>
More information about the Evolve-testers
mailing list