Mercurial > hg
view tests/test-sparse-clear.t @ 51626:865efc020c33 default tip
dirstate: remove the python-side whitelist of allowed matchers
This whitelist is too permissive because it allows matchers that contain
disallowed ones deep inside, for example through `intersectionmatcher`.
It is also too restrictive because it doesn't pass through
some of the matchers we support, such as `patternmatcher`.
It's also unnecessary because unsupported matchers raise
`FallbackError` and we fall back anyway.
Making this change makes more of the tests use rust code path,
and therefore subtly change behavior. For example, rust status
in largefiles repos seems to have strange behavior.
author | Arseniy Alekseyev <aalekseyev@janestreet.com> |
---|---|
date | Fri, 26 Apr 2024 19:10:35 +0100 |
parents | a6efb9180764 |
children |
line wrap: on
line source
test sparse $ hg init myrepo $ cd myrepo $ cat >> $HGRCPATH <<EOF > [extensions] > sparse= > purge= > strip= > rebase= > EOF $ echo a > index.html $ echo x > data.py $ echo z > readme.txt $ cat > base.sparse <<EOF > [include] > *.sparse > EOF $ hg ci -Aqm 'initial' $ cat > webpage.sparse <<EOF > %include base.sparse > [include] > *.html > EOF $ hg ci -Aqm 'initial' Clear rules when there are includes $ hg debugsparse --include *.py $ ls -A .hg data.py $ hg debugsparse --clear-rules $ ls -A .hg base.sparse data.py index.html readme.txt webpage.sparse Clear rules when there are excludes $ hg debugsparse -X base.sparse -X webpage.sparse $ ls -A .hg data.py index.html readme.txt $ hg debugsparse --clear-rules $ ls -A .hg base.sparse data.py index.html readme.txt webpage.sparse Clearing rules should not alter profiles $ hg debugsparse --enable-profile webpage.sparse $ ls -A .hg base.sparse index.html webpage.sparse $ hg debugsparse --include *.py $ ls -A .hg base.sparse data.py index.html webpage.sparse $ hg debugsparse --clear-rules $ ls -A .hg base.sparse index.html webpage.sparse