# HG changeset patch # User Kevin Bullock # Date 1358062756 21600 # Node ID d55e5d564d22deeec370d7d5007372c3476fcd65 # Parent ce275f3522b2a339039e27329f435daf4e47abfb filtering: rename filters to their antonyms Now that changelog filtering is in place, it's become evident that naming the filters according to the set of revs _not_ included in the filtered changelog is confusing. This is especially evident in the collaborative branch cache scheme. This changes the names of the filters to reflect the revs that _are_ included: hidden -> visible unserved -> served mutable -> immutable impactable -> base repoview.filteredrevs is renamed to filterrevs, so that callers read a bit more sensibly, e.g.: filterrevs('visible') # filter revs according to what's visible [ original upstream message ] diff -r ce275f3522b2 -r d55e5d564d22 tests/test-keyword.t --- a/tests/test-keyword.t Fri Jan 11 18:33:15 2013 +0000 +++ b/tests/test-keyword.t Sun Jan 13 01:39:16 2013 -0600 @@ -576,7 +576,7 @@ Commit and show expansion in original and copy $ hg --debug commit -ma2c -d '1 0' -u 'User Name ' - invalid branchheads cache (unserved): tip differs + invalid branchheads cache (served): tip differs c c: copy a:0045e12f6c5791aac80ca6cbfd97709a88307292 overwriting c expanding keywords @@ -760,10 +760,10 @@ | invalid here. $ hg --debug commit -l log -d '2 0' -u 'User Name ' - invalid branchheads cache (unserved): tip differs + invalid branchheads cache (served): tip differs a invalid branchheads cache: tip differs - invalid branchheads cache (unserved): tip differs + invalid branchheads cache (served): tip differs overwriting a expanding keywords committed changeset 2:bb948857c743469b22bbf51f7ec8112279ca5d83 $ rm log