mention limitation of --known
This commit is contained in:
parent
18efb40c85
commit
962f1f2363
2 changed files with 9 additions and 2 deletions
|
@ -36,8 +36,13 @@ needing to specify the dest file.
|
|||
|
||||
With this option, each specified src file is hashed using the default
|
||||
key-value backend (or the one specified with `--backend`), and if git-annex
|
||||
has a record of the file having been in the annex before, the content is
|
||||
reinjected.
|
||||
has a record of the resulting key having been in the annex before, the
|
||||
content is reinjected.
|
||||
|
||||
Note that, when using a key-value backend that includes the filename
|
||||
extension in the key, this will only work if the src files have the same
|
||||
extensions as the files with the same content that was originally added
|
||||
to git-annex.
|
||||
|
||||
Note that this will reinject old versions of files that have been
|
||||
modified or deleted from the current git branch.
|
||||
|
|
|
@ -5,3 +5,5 @@ I think it would be better if `git annex reinject --known` would ignore the file
|
|||
This problem does not affect `git annex reinject` without `--known`.
|
||||
|
||||
--spwhitton
|
||||
|
||||
> mentioned this on the git-annex reinject man page; [[done]] --[[Joey]]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue