summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar openmedi <openmedi@web>2016-10-18 17:37:38 +0000
committerGravatar admin <admin@branchable.com>2016-10-18 17:37:38 +0000
commit27cee0020c9d2b9d75389da39bc483ea226e0d09 (patch)
tree6cd0d198f1cb9b99d76e1655493df0ee6da96423 /doc
parent6d47996066dd7045eedfbf398580156cc49c4b31 (diff)
Added a comment
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/how_to_disaster_recovery/comment_7_7e08eb18e965f47782a39d0426b75b93._comment9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/forum/how_to_disaster_recovery/comment_7_7e08eb18e965f47782a39d0426b75b93._comment b/doc/forum/how_to_disaster_recovery/comment_7_7e08eb18e965f47782a39d0426b75b93._comment
new file mode 100644
index 000000000..7053bb282
--- /dev/null
+++ b/doc/forum/how_to_disaster_recovery/comment_7_7e08eb18e965f47782a39d0426b75b93._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="openmedi"
+ subject="comment 7"
+ date="2016-10-18T17:37:38Z"
+ content="""
+Not that I know of. I tried a whole bunch of things, like deleting remotes, killing processes trying to switch between repo versions, modes, playing around in config files etc. etc. Not all of them were smart ideas, I admit. At some point it worked and if I remember correctly I tried to delete a branch and then the problems started. But adjusted branches seems to me like a too advanced feature to use.
+
+Btw.: Skipping over these entries doesn't help for me. It still tries to repair the repo (which takes maybe 4 hours, including having to initiate a temporary repo).
+"""]]