This commit is contained in:
parent
ed40974ed9
commit
d204b882af
1 changed files with 14 additions and 0 deletions
|
@ -0,0 +1,14 @@
|
|||
I was testing out the fix/workaround for [[git-annex directory hashing problems on osx]] and I tried using the short forms of some of the commands i.e.
|
||||
|
||||
git annex copy -f externalusb .
|
||||
|
||||
which gives me
|
||||
|
||||
git-annex: user error (option `-f' is ambiguous; could be one of:
|
||||
-f --force allow actions that may lose annexed data
|
||||
-f REMOTE --from=REMOTE specify from where to transfer content
|
||||
|
||||
|
||||
I would have expected that since *--to* is the same as *-t* and *--from* is the same as *-f* as the in program documentation suggests. But *-f* clashes with the force command, I would suggest that the short form of *--force* be changed to *-F* and possibly rename the *Fast* commands to *Quick* and use *-Q* as the short form of the *Quick* operations. I didn't try the *-f* option with the move command, but it probably suffers from the same issue. It's probably better to avoid clashing short forms of command options.
|
||||
|
||||
I guess this issue is just a documentation issue and a minor interface change if needed and not a bug of git-annex, but a quirk.
|
Loading…
Reference in a new issue