[PATCH 2 of 2] discovery: properly filter changeset in 'peer.known' (issue4982)

[Augie Fackler]

On Mon, Dec 07, 2015 at 11:04:34AM -0800, Pierre-Yves David wrote:
>
>
> On 12/07/2015 11:03 AM, Augie Fackler wrote:
> >On Sun, Dec 06, 2015 at 02:20:59PM -0800, Gregory Szorc wrote:
> >>On Sun, Dec 6, 2015 at 2:10 PM, Pierre-Yves David <
> >>pierre-yves.david at ens-lyon.org> wrote:
> >
> >[...]
> >
> >>>>This should be marked BC because it changes semantics of the "known"
> >>>>wire protocol command. (The new semantics make sense to me modulo the
> >>>>bug described below.)
> >>>>
> >>>
> >>>Meh, this is fixing a bug in a wire protocol command that only affects
> >>>people using an experimental extensions. I do not think it deserve any
> >>>special flagging.
> >>>
> >>
> >>BC is BC. We want this to show up in the release notes so that anyone using
> >>an experimental or unknown 3rd party extension isn't confounded when 3.7
> >>changes behavior.
> >
> >+1, mark it BC to be safe.
>
> okay, can someone fix it inflight?

Queued with (BC) added.

>
>
> --
> Pierre-Yves David
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> https://selenic.com/mailman/listinfo/mercurial-devel