D6851: narrow: don't hexify paths and double-hexify known nodes on wire (BC)

[martinvonz (Martin von Zweigbergk)]

martinvonz added a comment.


  In D6851#100666 <https://phab.mercurial-scm.org/D6851#100666>, @idlsoft wrote:
  
  >> @idlsoft and their company does use narrow extension. @idlsoft can you upgrade server and client at the same time?
  >
  > I did that a little while ago to move to 5.0. It was not fun. It's server, teamcity, clients, docker images.
  > What operations does this affect? Regular `push/pull/clone` or only `tracked --add-include`?
  
  Just `tracked --add-include`. A workaround to simplify the upgrade would be to change `wireprototypes.SUPPORTED_ELLIPSESCAP` to be `(ELLIPSESCAP1, )` on the server from now until all clients have upgraded. But that may still be annoying and error-prone for you to deal with. @pulkit, I suppose we should just add a `exp-narrow-2` capability to deal with this? It doesn't seem fair to make @idlsoft deal with it.

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST ACTION
  https://phab.mercurial-scm.org/D6851/new/

REVISION DETAIL
  https://phab.mercurial-scm.org/D6851

To: martinvonz, durin42, #hg-reviewers
Cc: pulkit, idlsoft, mercurial-devel