From 73d9f91ecbcceccb51b8b5d8917871399609d1b1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 4 Feb 2016 12:32:04 -0400 Subject: [PATCH] response --- ...omment_1_dab5a92416314a7d4c02663d4e46cd60._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/Multisession_compatible__63__/comment_1_dab5a92416314a7d4c02663d4e46cd60._comment diff --git a/doc/forum/Multisession_compatible__63__/comment_1_dab5a92416314a7d4c02663d4e46cd60._comment b/doc/forum/Multisession_compatible__63__/comment_1_dab5a92416314a7d4c02663d4e46cd60._comment new file mode 100644 index 0000000000..9dc228316a --- /dev/null +++ b/doc/forum/Multisession_compatible__63__/comment_1_dab5a92416314a7d4c02663d4e46cd60._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-02-04T16:30:30Z" + content=""" +git-annex has quite extensive locking, so it's entirely safe to run any +combination of any git-annex commands at the same time. + +(It doesn't actually check out the git-annex branch when making commits to +it BTW.) +"""]]