context: retrieve hidden from filteredrevs
This prepare the dropping of the repo.hiddenrevs property
revset: retrieve hidden from filteredrevs
This prepare the dropping of the `repo.hiddenrevs` property
hidden: use both parents of working directory
If we are merging with and extinct revision, this extinct revision should not be
hidden.
hidden: drop cache on hiddenrevs property
The `filteredrevs` function already have a cache mechanism. And this cache in
invalidated at the same time than the current property cache. So we drop the
cache on the property.
The property itself is going to be dropped soon.
hidden: move computation in filter function
There is not good reason for this computation to be handle in a different way
from the other. We are moving the computation of hidden revs in the filter
function. In later changesets, code that access to `repo.hiddenrevs` will be
updated and the property dropped.
branchcache: add note about cache invalidation to test-keyword.t
[Should've been included in
aff706b3a21c.]
--Kevin Bullock <kbullock@ringworld.org>
clfilter: add impactable filter
The `mutable` filter still have some chance to get invalidated. This will happen
when:
- you garbage collect hidden changeset,
- public phase is moved backward,
- something is changed in the filtering (this could be fixed)
So we introduce an even more stable filtering set: everything with a revision
number egal or higher than the first mutable changeset is filtered.
The only official use of this filter is for branchcache.
clfilter: add mutable filtering
It filters all mutable changesets, leaving only public changeset unfiltered.
This filtering set is expected to be much more stable that the previous one as
public changeset are unlikely to disapear.
The only official use of this filter is for branchcache.