pulkit created this revision.
Herald added a reviewer: durin42.
Herald added a subscriber: mercurial-devel.
Herald added a reviewer: hg-reviewers.
REVISION SUMMARY
Recently we introduced narrow capabilities for the server. So we can check
whether a server has narrow clone support or not before
pulkit updated this revision to Diff 11503.
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
https://phab.mercurial-scm.org/D4789?vs=11472&id=11503
REVISION DETAIL
https://phab.mercurial-scm.org/D4789
AFFECTED FILES
hgext/narrow/narrowcommands.py
tests/test-narrow-clone-non-narrow-s
martinvonz added a comment.
> This is BC because new clients won't be able to extend from old
narrow-enabled servers.
I think your previous patch was also BC in that sense since it started
requiring the server to have the ellipses wire capability when widening with
ellipsis nodes. It's
pulkit updated this revision to Diff 11518.
pulkit edited the summary of this revision.
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
https://phab.mercurial-scm.org/D4789?vs=11503&id=11518
REVISION DETAIL
https://phab.mercurial-scm.org/D4789
AFFECTED FILES
hgext/narrow/narrowcomman
pulkit added a comment.
In https://phab.mercurial-scm.org/D4789#72717, @martinvonz wrote:
> > This is BC because new clients won't be able to extend from old
narrow-enabled servers.
>
> I think your previous patch was also BC in that sense since it started
requiring the server to hav
This revision was automatically updated to reflect the committed changes.
Closed by commit rHG06e75fbf9d6b: narrow: check for servers' narrow
support before doing anything (BC) (authored by pulkit, committed by ).
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
https://phab.mercurial-scm.
