From 5cbce5f308627a12a8ab9193aecc59d932faedb0 Mon Sep 17 00:00:00 2001 From: CandyAngel Date: Fri, 18 May 2018 08:55:31 +0000 Subject: [PATCH] --- ...a_move_has_force_option_described_twice.mdwn | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/g-a_move_has_force_option_described_twice.mdwn diff --git a/doc/bugs/g-a_move_has_force_option_described_twice.mdwn b/doc/bugs/g-a_move_has_force_option_described_twice.mdwn new file mode 100644 index 0000000000..2ba7c73335 --- /dev/null +++ b/doc/bugs/g-a_move_has_force_option_described_twice.mdwn @@ -0,0 +1,17 @@ +The **force** option in [[git-annex-move]] is described twice. + +* `--force` + + Override numcopies and required content checking, and always remove + files from the source repository once the destination repository has a + copy. + + Note that, even without this option, you can move the content of a file + from one repository to another when numcopies is not satisfied, as long + as the move does not result in there being fewer copies. + +* `--force` + + When moving content from a remote, ignore location tracking information + and always check if the remote has content. Can be useful if the location + tracking information is out of date.