aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/git-annex_merge_stalls
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/git-annex_merge_stalls')
-rw-r--r--doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment b/doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment
index 382f8c835..a0f452b5d 100644
--- a/doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment
+++ b/doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment
@@ -11,7 +11,7 @@ joeyh so, my thought is that perhaps you had a git-annex process before that was
joeyh for example, if you ran it and ctrl-z'd at just the right time, it could be suspended and holding the lock
joeyh (or the kernel coud have gotten confused, which given you also had a crash, who knows..)
dp sounds logical
-joeyh forcing locks is always a problimatic thing
+joeyh forcing locks is always a problematic thing
joeyh but git-annex could certainly notice if it seems to be stalled and print some useful messages
joeyh and maybe have a way to run with locks forced
</pre>