This is an archive of the discontinued Mercurial Phabricator instance.

narrow: check for servers' narrow support before doing anything (BC)
ClosedPublic

Authored by pulkit on Sep 28 2018, 4:58 PM.

Details

Summary

Recently we introduced narrow capabilities for the server. So we can check
whether a server has narrow clone support or not before doing anything. This is
BC because new clients won't be able to extend from old narrow-enabled servers.
I *think* narrow is not used much (maybe just inside Google), also it's
experimental so I think we can change this. We will need to this someday anyway.

The "doesn't" in error is changed to "does not" because I think that's we do in
core. I also changed one more instance of the error message to use 'does not'
for consistency.

Diff Detail

Repository
rHG Mercurial
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

pulkit created this revision.Sep 28 2018, 4:58 PM

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 not a problem for us to add that capability (we already have), but you may want to mention it there for consistency :), if I understood that right.

hgext/narrow/narrowcommands.py
137

Change "doesn't" to "does not" here too so it's consistent?

pulkit edited the summary of this revision. (Show Details)Oct 1 2018, 12:02 PM
pulkit updated this revision to Diff 11518.
pulkit added a comment.EditedOct 1 2018, 12:07 PM

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 not a problem for us to add that capability (we already have), but you may want to mention it there for consistency :), if I understood that right.

I am not sure whether that patch stands as a BC but yes, the whole rework and refactoring during this cycle make big BC's in how narrow extension work and I doubt that a client with hg-4.8 will be able to use narrow with server which is at hg-4.7.

martinvonz accepted this revision.Oct 2 2018, 12:19 PM
This revision is now accepted and ready to land.Oct 2 2018, 12:19 PM
This revision was automatically updated to reflect the committed changes.