From 0d555aa363482ed041db2d9c63da271ba7f4ced8 Mon Sep 17 00:00:00 2001 From: Yaroslav Halchenko Date: Wed, 1 Jun 2016 21:46:58 -0400 Subject: minor typo fixes throughout problematic flexibility --- .../comment_3_ced9b0d724fb55c756106b64c3721003._comment | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/bugs/git-annex_merge_stalls') 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 -- cgit v1.2.3