From 8f2547ef89be07317c209f74d1804e6f8a0e722e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 26 Oct 2016 14:04:59 -0400 Subject: [PATCH] comment --- ...nt_1_311a8a43d360074abd522fff14bfcb45._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/how_to_copy_tp_multiple_remotes_simultaneously__63__/comment_1_311a8a43d360074abd522fff14bfcb45._comment diff --git a/doc/bugs/how_to_copy_tp_multiple_remotes_simultaneously__63__/comment_1_311a8a43d360074abd522fff14bfcb45._comment b/doc/bugs/how_to_copy_tp_multiple_remotes_simultaneously__63__/comment_1_311a8a43d360074abd522fff14bfcb45._comment new file mode 100644 index 0000000000..9661ac5f1f --- /dev/null +++ b/doc/bugs/how_to_copy_tp_multiple_remotes_simultaneously__63__/comment_1_311a8a43d360074abd522fff14bfcb45._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-10-26T18:02:43Z" + content=""" +You need to provide more detail about "lock contention on `.git/config`". +Ideally an actual error message. + +Normally it's perfectly fine to run multiple `git annex copy`, or any +other git-annex command for that matter. + +And the only thing I know of that locks .git/config is when the +configuration is being changed, which doesn't normally happen when +copying to a remote, unless perhaps this remote has never been used before. +"""]]