diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-03-19 16:39:31 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-03-19 16:39:31 -0400 |
| commit | fda5243b91337d32de8aed039a4201056bcb7ccf (patch) | |
| tree | 09da1966102444994a0bec0c843833d338bf7998 | |
| parent | 8feff09e84001be89b2ae2afe6219d2458c208ff (diff) | |
close
| -rw-r--r-- | doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone..mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone..mdwn b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone..mdwn index e01310336..0d442437d 100644 --- a/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone..mdwn +++ b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone..mdwn @@ -228,3 +228,13 @@ Everything up-to-date """]] Well, I see that thing about "failed to lock". I can imagine that my 'killall git-annex' to kill a leftover process that was hanging around after I'd done git-annex assistant --stop might have left stale lock files, somewhere... but of course I only got as far as doing that because I was already encountering problems, just trying to return to the webapp. + +> The original bug report seems to be a case of user confusion, +> and not a bug. (Although perhaps the UI is confusing?) +> +> The "resource exhausted" that came up later is quite likely the problem +> fixed in [[!commit 4d06037fdd44ba38fcd4c118d1e6330f06e22366]], +> which affected local git remotes. +> +> [[closing|done]]; I don't see any value keeping this open, I'm afraid. +> --[[Joey]] |