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

Augie Fackler raf at durin42.com
Mon Dec 7 13:03:49 CST 2015


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.


More information about the Mercurial-devel mailing list