diff options
Diffstat (limited to 'doc/design/adjusted_branches.mdwn')
-rw-r--r-- | doc/design/adjusted_branches.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/design/adjusted_branches.mdwn b/doc/design/adjusted_branches.mdwn index 73c66ff74..ba3e78421 100644 --- a/doc/design/adjusted_branches.mdwn +++ b/doc/design/adjusted_branches.mdwn @@ -206,6 +206,9 @@ reverse filter to draw the wrong conclusion. Maybe look at a list of what objects were not present when applying the filter, and use that to decide which to not delete when reversing it? +So, a reverse filter may need some state that was collected when running +the filter forwards, in order to decide what to do. + ## push The new master branch can then be pushed out to remotes. The @@ -273,6 +276,8 @@ adjusting filter, albeit an extreme one. This might improve view branches. For example, it's not currently possible to update a view branch with changes fetched from a remote, and this could get us there. +This would need the reverse filter to be able to change metadata. + [WORKTREE: Wouldn't be able to integrate, unless view branches are changed into adjusted view worktrees.] |