[PATCH 4 of 8] discovery: move undecided set on the partialdiscovery

Pulkit Goyal 7895pulkit at gmail.com
Fri Jan 4 16:03:21 UTC 2019


On Mon, Dec 31, 2018 at 11:11 PM Boris Feld <boris.feld at octobus.net> wrote:

> # HG changeset patch
> # User Boris Feld <boris.feld at octobus.net>
> # Date 1545963817 -3600
> #      Fri Dec 28 03:23:37 2018 +0100
> # Node ID 6eb53e3f1bc514d4cb376d84b2bdd1302d27f8e2
> # Parent  d4896a8672cb719ac2cf43f1a7035a335e43665c
> # EXP-Topic discovery-refactor
> # Available At https://bitbucket.org/octobus/mercurial-devel/
> #              hg pull https://bitbucket.org/octobus/mercurial-devel/ -r
> 6eb53e3f1bc5
> discovery: move undecided set on the partialdiscovery
>
> To initialize it, we need to know the discovery target. This commit only
> move
> the set on the `partialdiscovery` object, later changeset will take
> advantage of
> it.
>
> diff --git a/mercurial/setdiscovery.py b/mercurial/setdiscovery.py
> --- a/mercurial/setdiscovery.py
> +++ b/mercurial/setdiscovery.py
> @@ -167,12 +167,16 @@ class partialdiscovery(object):
>      Feed with data from the remote repository, this object keep track of
> the
>      current set of changeset in various states:
>
> -    - common: own nodes I know we both know
> +    - common: exist both locally and remotely
> +    - common:    own nodes I know we both know
> +    - undecided: own nodes where I don't know if remote knows them
>      """
>

the above documentation too.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20190104/63549e37/attachment.html>


More information about the Mercurial-devel mailing list