maybe call it unlock and not checkout
It'd be confusing to have a git-annex subcommand with the same name as a git subcommand.
This commit is contained in:
parent
75d2925082
commit
d56feda25d
4 changed files with 19 additions and 18 deletions
|
@ -4,4 +4,4 @@ In particular, while files can be added using it, git-annex will not notice
|
|||
when their content changes, and will not create a new key for the new sha1
|
||||
of the net content.
|
||||
|
||||
[[done]]; use checkout subcommand
|
||||
[[done]]; use unlock subcommand and commit changes with git
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue