From efa45425f70b8bc67971c9578486bf37749f21f8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 9 Feb 2015 18:45:46 -0400 Subject: comment --- .../comment_7_fc56ec87725c7427794b70ee2ba2822a._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/git-annex_branch_shows_commit_with_looong_commitlog/comment_7_fc56ec87725c7427794b70ee2ba2822a._comment (limited to 'doc/bugs/git-annex_branch_shows_commit_with_looong_commitlog') diff --git a/doc/bugs/git-annex_branch_shows_commit_with_looong_commitlog/comment_7_fc56ec87725c7427794b70ee2ba2822a._comment b/doc/bugs/git-annex_branch_shows_commit_with_looong_commitlog/comment_7_fc56ec87725c7427794b70ee2ba2822a._comment new file mode 100644 index 000000000..cd7510140 --- /dev/null +++ b/doc/bugs/git-annex_branch_shows_commit_with_looong_commitlog/comment_7_fc56ec87725c7427794b70ee2ba2822a._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 7""" + date="2015-02-09T22:44:50Z" + content=""" +The only other thing I can think to do about this is to make git-annex block +direct pushes to the git-annex branch, by setting up a pre-receive hook. + +Then, there should be no way for the race to occur +(except for a locking failure, or a pull into the branch?), +and git-annex wouldn't need to check for it +"""]] -- cgit v1.2.3