2fb3722ce9
* When annex objects are received into git repositories, their checksums are verified then too. * To get the old, faster, behavior of not verifying checksums, set annex.verify=false, or remote.<name>.annex-verify=false. * setkey, rekey: These commands also now verify that the provided file matches the key, unless annex.verify=false. * reinject: Already verified content; this can now be disabled by setting annex.verify=false. recvkey and reinject already did verification, so removed now duplicate code from them. fsck still does its own verification, which is ok since it does not use getViaTmp, so verification doesn't happen twice when using fsck --from.
29 lines
531 B
Markdown
29 lines
531 B
Markdown
# NAME
|
|
|
|
git-annex setkey - sets annexed content for a key
|
|
|
|
# SYNOPSIS
|
|
|
|
git annex setkey key file
|
|
|
|
# DESCRIPTION
|
|
|
|
This plumbing-level command makes the content of the specified key
|
|
be set to the specified file. The file is moved into the annex.
|
|
|
|
It's generally a better idea to use [[git-annex-reinject]](1) instead of
|
|
this command.
|
|
|
|
# SEE ALSO
|
|
|
|
[[git-annex]](1)
|
|
|
|
[[git-annex-reinject]](1)
|
|
|
|
[[git-annex-dropkey]](1)
|
|
|
|
# AUTHOR
|
|
|
|
Joey Hess <id@joeyh.name>
|
|
|
|
Warning: Automatically converted into a man page by mdwn2man. Edit with care.
|