D6848: narrow: add option for automatically removing unused includes
martinvonz (Martin von Zweigbergk)
phabricator at mercurial-scm.org
Fri Sep 13 17:16:47 EDT 2019
martinvonz added inline comments.
INLINE COMMENTS
> rdamazio wrote in test-narrow.t:457
> This obsolete commit is completely lost afterwards, which kind of violates the principle of "all changes are kept forever" - should it dump this somewhere for safekeeping?
> Also, what if you just don't get rid of the files, and simply remove it from the narrowspec? It'll stop processing/pulling/pushing the directory, but no data is lost.
> This obsolete commit is completely lost afterwards, which kind of violates the principle of "all changes are kept forever" - should it dump this somewhere for safekeeping?
Yes, it does dump it to a backup bundle (see output on line 474).
> Also, what if you just don't get rid of the files, and simply remove it from the narrowspec? It'll stop processing/pulling/pushing the directory, but no data is lost.
That's just about the working directory, right? This file is unchanged in the working directory at the time of `hg tracked --auto-remove-includes`...
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST ACTION
https://phab.mercurial-scm.org/D6848/new/
REVISION DETAIL
https://phab.mercurial-scm.org/D6848
To: martinvonz, durin42, #hg-reviewers
Cc: rdamazio, mercurial-devel
More information about the Mercurial-devel
mailing list