[PATCH 7 of 8] discovery: move missing tracking inside the partialdiscovery object

Pulkit Goyal 7895pulkit at gmail.com
Fri Jan 4 16:05:10 UTC 2019


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

> # HG changeset patch
> # User Boris Feld <boris.feld at octobus.net>
> # Date 1545965280 -3600
> #      Fri Dec 28 03:48:00 2018 +0100
> # Node ID c5c3e376d7afcb5972f72262d84b6d4b75645329
> # Parent  b1294a6cb1b4c1d30ef9840bf023b95337603158
> # EXP-Topic discovery-refactor
> # Available At https://bitbucket.org/octobus/mercurial-devel/
> #              hg pull https://bitbucket.org/octobus/mercurial-devel/ -r
> c5c3e376d7af
> discovery: move missing tracking inside the partialdiscovery object
>
> This is the final set that we need to track to have a fully up to date
> information within the object.
>
> diff --git a/mercurial/setdiscovery.py b/mercurial/setdiscovery.py
> --- a/mercurial/setdiscovery.py
> +++ b/mercurial/setdiscovery.py
> @@ -170,6 +170,7 @@ class partialdiscovery(object):
>      - 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
> +    - missing:   own nodes I know remote lacks
>      """
>
same, can you replace "I" and "own" with better words, maybe local
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20190104/ccbdd485/attachment.html>


More information about the Mercurial-devel mailing list