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

[martinvonz (Martin von Zweigbergk)]

martinvonz added a comment.


  In D6851#100690 <https://phab.mercurial-scm.org/D6851#100690>, @idlsoft wrote:
  
  >>> 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.
  >>
  >> Sounds like a good idea!
  >
  > If it's just `tracked --add-include` then it's not a big deal, it won't disrupt regular flow.
  > If backward compatibility doesn't complicate the code - great, if not - don't worry about it.
  
  It does seem to be more work than I hoped at first, so it would be very much appreciated if you can live with `hg tracked --add-include` (and `--remove-exclude`) not working while you transition server and clients.

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