diff options
| -rw-r--r-- | doc/forum/how_to_disaster_recovery/comment_7_7e08eb18e965f47782a39d0426b75b93._comment | 9 | ||||
| -rw-r--r-- | doc/forum/how_to_disaster_recovery/comment_8_78720819bea58f30146451dd953f10a5._comment | 7 |
2 files changed, 16 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). +"""]] diff --git a/doc/forum/how_to_disaster_recovery/comment_8_78720819bea58f30146451dd953f10a5._comment b/doc/forum/how_to_disaster_recovery/comment_8_78720819bea58f30146451dd953f10a5._comment new file mode 100644 index 000000000..1eb369466 --- /dev/null +++ b/doc/forum/how_to_disaster_recovery/comment_8_78720819bea58f30146451dd953f10a5._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="openmedi" + subject="comment 8" + date="2016-10-18T17:38:53Z" + content=""" +The \"at some point\" portion of my previous message refers to a state before the problems started, not after or in between. Sorry for being unclear. +"""]] |