From 51c9f18fafe83ec7655bbc2e6645b11355415549 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 15 Jan 2016 15:17:06 -0400 Subject: [PATCH] response --- ...ment_3_94b4efa49efbee741c051227b3204562._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/basic_usage_questions/comment_3_94b4efa49efbee741c051227b3204562._comment diff --git a/doc/forum/basic_usage_questions/comment_3_94b4efa49efbee741c051227b3204562._comment b/doc/forum/basic_usage_questions/comment_3_94b4efa49efbee741c051227b3204562._comment new file mode 100644 index 0000000000..604903aa0e --- /dev/null +++ b/doc/forum/basic_usage_questions/comment_3_94b4efa49efbee741c051227b3204562._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2016-01-15T19:14:07Z" + content=""" +You can use git's post-receive hook to run `git annex merge` to update a +direct mode repository. See example in +[[tips/setup_a_public_repository_on_a_web_site]]. + +It's fine to use --force with dropunused if you really want to force +deleting the only copy of a file. git-annex will never delete the last copy +of a file without being forced as a safety measure. +"""]]