mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

updates

Browse source
This commit is contained in:
Joey Hess 2016-02-23 13:21:38 -04:00
parent ae0a10618b
commit 2bf90c7b56
Failed to extract signature
1 changed files with 5 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
doc/design/adjusted_branches.mdwn
View file

@ -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 objects were not present when applying the filter, and use that to decide
which to not delete when reversing it? 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 ## push
The new master branch can then be pushed out to remotes. The 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 For example, it's not currently possible to update a view branch with
changes fetched from a remote, and this could get us there. 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 [WORKTREE: Wouldn't be able to integrate, unless view branches are changed
into adjusted view worktrees.] into adjusted view worktrees.]