comparison mercurial/narrowspec.py @ 46606:ced66295ea90

narrow: remove assertion about working copy being clean The user can always modify the working copy, including while they're running `hg tracked --remove-include <path>`. Nothing really bad happens when they do that, and we already have code for printing a nice warning, so we can safely remove the assertion we had. Differential Revision: https://phab.mercurial-scm.org/D10063
author Martin von Zweigbergk <martinvonz@google.com>
date Tue, 23 Feb 2021 22:58:30 -0800
parents 89a2afe31e82
children e4ccc341e65b
comparison
equal deleted inserted replaced
46605:946a07f08906 46606:ced66295ea90
327 removedmatch, subrepos=[], ignored=True, clean=True, unknown=True 327 removedmatch, subrepos=[], ignored=True, clean=True, unknown=True
328 ) 328 )
329 trackeddirty = status.modified + status.added 329 trackeddirty = status.modified + status.added
330 clean = status.clean 330 clean = status.clean
331 if assumeclean: 331 if assumeclean:
332 assert not trackeddirty
333 clean.extend(lookup) 332 clean.extend(lookup)
334 else: 333 else:
335 trackeddirty.extend(lookup) 334 trackeddirty.extend(lookup)
336 _deletecleanfiles(repo, clean) 335 _deletecleanfiles(repo, clean)
337 uipathfn = scmutil.getuipathfn(repo) 336 uipathfn = scmutil.getuipathfn(repo)