summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Marco <Marco@web>2015-07-25 18:10:09 +0000
committerGravatar admin <admin@branchable.com>2015-07-25 18:10:09 +0000
commit6c85081d6a6b2476e4fd709482c42351d58193c8 (patch)
tree7d38d37fd26fe17ad9fd1cbf75c8e8f2a694e513
parentd16e6da40e6351d6cf1257a91aa824ece77732a1 (diff)
Added a comment: How to debug?
-rw-r--r--doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_5_4343ee35e4091fc50268f9fc611f5148._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_5_4343ee35e4091fc50268f9fc611f5148._comment b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_5_4343ee35e4091fc50268f9fc611f5148._comment
new file mode 100644
index 000000000..0ec137081
--- /dev/null
+++ b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_5_4343ee35e4091fc50268f9fc611f5148._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="Marco"
+ subject="How to debug?"
+ date="2015-07-25T18:10:08Z"
+ content="""
+I want to give the two assistants one more try with the newest version.
+
+But I want the assistant not to try a repair once a failure is detected. I want to check the state of the repository to get a clue what goes wrong.
+As I understood the code there is no configuration to prevent the repair. Am I wrong? If not I could try to introduce one if it makes sense.
+"""]]