From d7f671e471904ae6d57631fe9c0b0b7b275a11e0 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 6 Jul 2015 14:51:13 -0400 Subject: [PATCH] respinse --- ..._182c66e98086dbfde29b615d0cf0e8e4._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/forum/Question:_git-annex-only_repo___63__/comment_9_182c66e98086dbfde29b615d0cf0e8e4._comment diff --git a/doc/forum/Question:_git-annex-only_repo___63__/comment_9_182c66e98086dbfde29b615d0cf0e8e4._comment b/doc/forum/Question:_git-annex-only_repo___63__/comment_9_182c66e98086dbfde29b615d0cf0e8e4._comment new file mode 100644 index 0000000000..b9432bb03c --- /dev/null +++ b/doc/forum/Question:_git-annex-only_repo___63__/comment_9_182c66e98086dbfde29b615d0cf0e8e4._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 9""" + date="2015-07-06T18:47:23Z" + content=""" +If you use indirect mode, and avoid passing --force to any git-annex +commands, then git-annex will ensure that it always keeps all versions of +all files. + +Any command that would delete any data requires the --force option. + +If your repo uses direct mode, we can't make this guarantee, because +the files are left directly in your work tree and you can edit or delete +them manually and there's nothing git-annex can do to stop that. + +There is not currently a way to keep a particular number of old versions of +a file. This comes down to picking the versions to keep or drop when +running `git annex dropunused` (with --force of course). +"""]]