diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-03-18 20:07:59 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-03-18 20:07:59 -0400 |
| commit | c76bcdc47e0d4a48b9b9cc91718255e89c535d05 (patch) | |
| tree | 2aed28a0de95f8b8b2d0c2d440c2917b884ea2f3 /doc/bugs/watcher_commits_unlocked_files.mdwn | |
| parent | a46424e78b1cd98f87ee62a49b63acff7e6d890c (diff) | |
bug triaging and tagging
Diffstat (limited to 'doc/bugs/watcher_commits_unlocked_files.mdwn')
| -rw-r--r-- | doc/bugs/watcher_commits_unlocked_files.mdwn | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/bugs/watcher_commits_unlocked_files.mdwn b/doc/bugs/watcher_commits_unlocked_files.mdwn index 37c79e353..37e50fca0 100644 --- a/doc/bugs/watcher_commits_unlocked_files.mdwn +++ b/doc/bugs/watcher_commits_unlocked_files.mdwn @@ -28,3 +28,10 @@ Possible approaches: how to find the file to unlock it. [[!meta title="assistant: watcher_commits_unlocked_files"]] + +> [[done]]; I just tested and somehow this no longer happens; +> the watcher/assistant leaves the unlocked file alone, and then +> as soon as it's modified re-adds it. +> +> Also, of course, there is direct mode, which avoids needing to unlock... +> --[[Joey]] |