[PATCH 2 of 2 V2] streamclone: abort when client needs to handle obsmarkers, but doesn't

Anton Shestakov av6 at dwimlabs.net
Thu Nov 1 03:59:04 UTC 2018


On Wed, 31 Oct 2018 12:48:49 -0700
Gregory Szorc <gregory.szorc at gmail.com> wrote:

> On Thu, Oct 18, 2018 at 6:53 AM Anton Shestakov <av6 at dwimlabs.net> wrote:
> 
> > # HG changeset patch
> > # User Anton Shestakov <av6 at dwimlabs.net>
> > # Date 1538754012 -28800
> > #      Fri Oct 05 23:40:12 2018 +0800
> > # Node ID 7827e8870afe4a1505767a748dd07e94569196ac
> > # Parent  212b1f69138c7d1fa166356448305219259f34f9
> > # EXP-Topic stream-obsmarkers
> > streamclone: abort when client needs to handle obsmarkers, but doesn't
> >
> > When client doesn't have any of obsolescence markers exchange capabilities,
> > then it's safe to say it can't handle obsmarkers. However, if it
> > understands
> > even one format version, then stream clones are fine -- client can use
> > "obsmarkers" bundle2 part.
> >  
> 
> I'm tempted to say we should try to get this into 4.8.

Looks like it was quietly pushed before 4.8rc0 was cut, so it's in.


More information about the Mercurial-devel mailing list