git-filter-repo/t
Elijah Newren 7eaaf191de filter-repo: correctly prune nested tags not matching filtering criteria
When the user specifies some kind of criteria to filter commits by (e.g.
--subdirectory-filter mysubdir), we rewrite parents commits that are
entirely filtered out to the most recent ancestor that still exists, or
just prune the parent if there isn't one.  That works great when the
parent is a commit, but nested tags have parents that are tags.  If we
only prune the first tag (i.e. the tag of a commit), then letting any
tags through that had that tag as a parent will result in a fast-import
crash with a message of the form

   fatal: mark :35390 not declared

Ensure that when a tag gets pruned, the pruning is recorded as such...so
that any children tags will get pruned as well.

Signed-off-by: Elijah Newren <newren@gmail.com>
2020-10-17 12:14:18 -07:00
..
t9390 filter-repo: use new --date-format=raw-permissive fast-import option 2020-07-07 09:38:34 -06:00
t9391 Fix undefined variable names 2020-07-27 09:49:43 -07:00
run_coverage run_coverage: prefer coverage3 to python3-coverage 2019-11-21 16:19:26 -08:00
t9390-filter-repo.sh filter-repo: correctly prune nested tags not matching filtering criteria 2020-10-17 12:14:18 -07:00
t9391-filter-repo-lib-usage.sh filter-repo: use more expensive prunability checks when needed 2020-03-23 14:55:07 -07:00
t9392-python-callback.sh filter-repo (python3): replace strings with bytestrings 2019-05-08 08:57:51 -07:00
test-lib-functions.sh filter-repo: add some basic tests, with git-style test-lib.sh 2019-03-12 14:19:38 -07:00
test-lib.sh filter-repo: add some basic tests, with git-style test-lib.sh 2019-03-12 14:19:38 -07:00