mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

followup

Browse source
This commit is contained in:
Joey Hess 2018-05-21 12:51:55 -04:00
parent 9a9fa06d12
commit ca6f5be284
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/bugs/g-a_move_has_force_option_described_twice/comment_1_1ff90a7b1df3ebad2e1f17726d7d4fd7._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-05-21T16:42:51Z"
content="""
Worse, it's forcing two unrelated behaviors and the user may only
want one of them.
The numcopies check override --force was only recently
added.
The location tracking ignore --force is older, but is unlike
other uses of --force in git-annex. It's so off the radar that it was an
undocumented option from 2013 until I noticed the documentation was missing
in 2017! Also, it's not clear if/when anyone would use that. Seems like
running `git annex sync` first would be more efficient and have the same
result.
So, I'm inclined to keep the numcopies check --force, which matches other
uses of --force in git-annex (eg drop --force), and remove the other
--force behavior, or make it be a differently named option. --slow
would be a good name, by contrast with move --fast.
"""]]