checked getKeysPresent; it's ok for v6 unlocked files
When a v6 unlocked files is removed from the work tree, unused doesn't show it. When it gets removed from the index, unused does show it. This is the same as a locked file.
This commit is contained in:
parent
e7183d83d3
commit
1dad3af3fc
2 changed files with 3 additions and 4 deletions
|
@ -744,9 +744,9 @@ data KeyLocation = InAnnex | InRepository
|
||||||
|
|
||||||
{- List of keys whose content exists in the specified location.
|
{- List of keys whose content exists in the specified location.
|
||||||
|
|
||||||
- InAnnex only lists keys under .git/annex/objects,
|
- InAnnex only lists keys with content in .git/annex/objects,
|
||||||
- while InRepository, in direct mode, also finds keys located in the
|
- while InRepository, in direct mode, also finds keys with content
|
||||||
- work tree.
|
- in the work tree.
|
||||||
-
|
-
|
||||||
- Note that InRepository has to check whether direct mode files
|
- Note that InRepository has to check whether direct mode files
|
||||||
- have goodContent.
|
- have goodContent.
|
||||||
|
|
|
@ -345,7 +345,6 @@ files to be unlocked, while the indirect upgrades don't touch the files.
|
||||||
when pushing changes committed in such a repo. Ideally, should avoid
|
when pushing changes committed in such a repo. Ideally, should avoid
|
||||||
committing implicit unlocks, or should prevent such commits leaking out
|
committing implicit unlocks, or should prevent such commits leaking out
|
||||||
in pushes.
|
in pushes.
|
||||||
* getKeysPresent needs to check if object file is modified
|
|
||||||
|
|
||||||
----
|
----
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue