summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-11-10 11:32:28 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-11-10 11:32:28 -0400
commitca6bfa0691228480cc8de4bd697bc3c23a576f65 (patch)
tree0c47f69053057926f798a3cb20a0c9b2b1517b0a
parentfad74f80e4464ed3cb12b1df3ac6a48c0c93240f (diff)
response
-rw-r--r--doc/bugs/git-annex_doesn__39__t_work_on_lustre:_waitToSetLock:_unsupported_operation___40__Function_not_implemented__41__/comment_9_9f6b04e9f155d289e8330b444585444f._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_doesn__39__t_work_on_lustre:_waitToSetLock:_unsupported_operation___40__Function_not_implemented__41__/comment_9_9f6b04e9f155d289e8330b444585444f._comment b/doc/bugs/git-annex_doesn__39__t_work_on_lustre:_waitToSetLock:_unsupported_operation___40__Function_not_implemented__41__/comment_9_9f6b04e9f155d289e8330b444585444f._comment
new file mode 100644
index 000000000..d7c331bee
--- /dev/null
+++ b/doc/bugs/git-annex_doesn__39__t_work_on_lustre:_waitToSetLock:_unsupported_operation___40__Function_not_implemented__41__/comment_9_9f6b04e9f155d289e8330b444585444f._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 9"""
+ date="2015-11-10T15:25:58Z"
+ content="""
+git uses dot-locks (.git/index.lck).
+
+I need to understand why multiple Lustre users seem to have it configured
+in a way that doesn't allow using the locking capabilities that are built
+into it. Maybe there's a good reason they do that; but adding ugly top-level
+dot locking to git-annex without a good reason could be a bad mistake.
+"""]]