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