[PATCH 17 of 17] obsolescence: add test for the "branch replacement" logic during push, case D6

Yuya Nishihara yuya at tcha.org
Sat Apr 15 03:42:52 EDT 2017


On Fri, 14 Apr 2017 11:38:35 -0700, Sean Farley wrote:
> Pierre-Yves David <pierre-yves.david at ens-lyon.org> writes:
> 
> > # HG changeset patch
> > # User Pierre-Yves David <pierre-yves.david at ens-lyon.org>
> > # Date 1492093695 -7200
> > #      Thu Apr 13 16:28:15 2017 +0200
> > # Node ID d106f22c0f397303727ce045698076a3dc4474ba
> > # Parent  6020bb1b76c86bf0b42b174c3348f98e5909e0b2
> > # EXP-Topic push.checkheads
> > # Available At https://www.mercurial-scm.org/repo/users/marmoute/mercurial/
> > #              hg pull https://www.mercurial-scm.org/repo/users/marmoute/mercurial/ -r d106f22c0f39
> > obsolescence: add test for the "branch replacement" logic during push, case D6
> >
> > Mercurial checks for the introduction of new heads on push. Evolution comes
> > into play to detect if existing branches on the server are being replaced by
> > some of the new one we push.
> >
> > The current code for this logic is very basic (eg: issue4354) and was poorly
> > tested. We have a better implementation coming in the evolve extension fixing
> > these issues and with more serious tests coverage. In the process of upstreaming
> > this improved logic, we start with adding the test case that are already passing
> > with the current implementation. Once they are all in, we'll upstream the better
> > implementation and the extra test cases.
> >
> > See inline documentation for details about the test case added in this
> > changeset.
> 
> Sure, seems fine to me again.

Queued per review, thanks.


More information about the Mercurial-devel mailing list