not a bug
This commit is contained in:
parent
a8b25288a1
commit
8065d195be
2 changed files with 21 additions and 0 deletions
|
@ -32,3 +32,4 @@ $> echo MD5E-s11--74d80f7dsd99b835e5189948c8d4297efdsdfsdf | git annex dropkey -
|
||||||
|
|
||||||
[[!meta author=yoh]]
|
[[!meta author=yoh]]
|
||||||
|
|
||||||
|
> [[notabug|done]] --[[Joey]]
|
||||||
|
|
|
@ -0,0 +1,20 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 1"""
|
||||||
|
date="2016-05-03T17:03:25Z"
|
||||||
|
content="""
|
||||||
|
Note that dropkey does *not* check if other copies exist, so the --force is
|
||||||
|
unncessary; eg it's always forced by default.
|
||||||
|
|
||||||
|
Anyway, dropkey will indicate a failure if it's actually unable to drop the
|
||||||
|
content for some reason, eg a permissions problem or the content is locked
|
||||||
|
to prevent it being dropped right now, or other unanticipated error.
|
||||||
|
But, if the content of the key is not present, it's successfully
|
||||||
|
gotten the repo into the requested state.
|
||||||
|
|
||||||
|
Similarly, git-annex transferkey will return success if the key it was
|
||||||
|
supposed to download is already present.
|
||||||
|
|
||||||
|
I don't consider this a bug, although am willing to be convinced
|
||||||
|
otherwise..
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue