summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar CandyAngel <CandyAngel@web>2015-06-04 12:18:20 +0000
committerGravatar admin <admin@branchable.com>2015-06-04 12:18:20 +0000
commit7d99b58af927c30fd3ba0e1b3b5b076b1479f344 (patch)
tree77d6838a169cd4bded74142558be5a8a25594843
parent3458db42d3df02ae847521b989388936ca6e6caa (diff)
Added a comment
-rw-r--r--doc/bugs/metadata_view_does_not_vpop_to_original_view/comment_7_a5511e21ee6c09d8edf2bca48482d848._comment9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/bugs/metadata_view_does_not_vpop_to_original_view/comment_7_a5511e21ee6c09d8edf2bca48482d848._comment b/doc/bugs/metadata_view_does_not_vpop_to_original_view/comment_7_a5511e21ee6c09d8edf2bca48482d848._comment
new file mode 100644
index 000000000..cbfa90038
--- /dev/null
+++ b/doc/bugs/metadata_view_does_not_vpop_to_original_view/comment_7_a5511e21ee6c09d8edf2bca48482d848._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="CandyAngel"
+ subject="comment 7"
+ date="2015-06-04T12:18:20Z"
+ content="""
+If I were in this situation, I would clone the broken repo, check the symlinks look correct in the clone, 'git annex reinit' it with the broken repos UUID, move .git/annex/objects to the clone, fsck and replace the broken one with the clone (just move the broken one aside if you want to keep it around).
+
+I don't think you can lose any data this way. Though any files you added while in the view (which you shouldn't do anyway) will be present in the annex, but have no symlink (they will show up in 'unused').
+"""]]