safer inannex checking
git-annex-shell inannex now returns always 0, 1, or 100 (the last when it's unclear if content is currently in the index due to it currently being moved or dropped). (Actual locking code still not yet written.)
This commit is contained in:
parent
2934a65ac5
commit
d3e1a3619f
14 changed files with 93 additions and 50 deletions
|
@ -26,7 +26,7 @@ module Remote (
|
|||
showTriedRemotes,
|
||||
showLocations,
|
||||
forceTrust,
|
||||
remoteHasKey
|
||||
logStatus
|
||||
) where
|
||||
|
||||
import qualified Data.Map as M
|
||||
|
@ -230,7 +230,7 @@ forceTrust level remotename = do
|
|||
- in the local repo, not on the remote. The process of transferring the
|
||||
- key to the remote, or removing the key from it *may* log the change
|
||||
- on the remote, but this cannot always be relied on. -}
|
||||
remoteHasKey :: Remote Annex -> Key -> Bool -> Annex ()
|
||||
remoteHasKey remote key present = logChange key (uuid remote) status
|
||||
logStatus :: Remote Annex -> Key -> Bool -> Annex ()
|
||||
logStatus remote key present = logChange key (uuid remote) status
|
||||
where
|
||||
status = if present then InfoPresent else InfoMissing
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue