D5278: narrow: detect if narrowspec was changed in a different share

[martinvonz (Martin von Zweigbergk)]

martinvonz added a comment.


  In https://phab.mercurial-scm.org/D5278#78697, @yuja wrote:
  
  > > 1. d1/f, d3/f, d3/g and d5/f should no longer be reported $ hg -R main files +  not deleting possibly dirty file d3/f +  not deleting possibly dirty file d3/g +  not deleting possibly dirty file d5/f
  >
  > I don't think it's good idea that any read-only commands can update working-copy
  >  files. And I suspect the narrowing/widening process could get complicated if
  >  merge/rebase were underway.
  >
  > Instead, can't we take the repository as dirty/unfinished state if local
  >  narrowspec differs from store's? The user will have to run some command to
  >  narrow/widen the working directory. Maybe he can also restore narrowspec of
  >  the store to finish ongoing merge/rebase.
  
  
  That's reasonable. I'll make this instead abort if the narrowspecs don't match and I'll add a `hg tracked --update-working-copy` or something like that.

REPOSITORY
  rHG Mercurial

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

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