summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-09-21 12:47:43 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-09-21 12:47:43 -0400
commitb6a9189c05ca5415f352ca309291992d130b9944 (patch)
tree357f521e34d5780450399b1c2ba37eda703f2903
parentd022468ab13f8b9b2baabcf8c5220ed3492e4aab (diff)
response
-rw-r--r--doc/forum/Central_server_with_automatically_merged_working_tree/comment_1_bc850e25e48598a09353850021c6368c._comment17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/forum/Central_server_with_automatically_merged_working_tree/comment_1_bc850e25e48598a09353850021c6368c._comment b/doc/forum/Central_server_with_automatically_merged_working_tree/comment_1_bc850e25e48598a09353850021c6368c._comment
new file mode 100644
index 000000000..2680a1411
--- /dev/null
+++ b/doc/forum/Central_server_with_automatically_merged_working_tree/comment_1_bc850e25e48598a09353850021c6368c._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-09-21T16:42:29Z"
+ content="""
+A way to do this pretty cleanly is described here:
+<http://git-annex.branchable.com/tips/setup_a_public_repository_on_a_web_site/>
+
+The annex-content hook is not meant to be run when a regular git push
+is made to the repository. That would be unnecessarily redundant with
+existing git hooks.
+
+I'd expect it to be pretty safe to edit files in such a repository,
+but you have to keep in mind that if changes are pushed into it at the same
+time as an edit is occuring, you can get into various situations with the
+hooks etc.
+"""]]