From e1bec1344326a3e966dc254e872d6393997e43dc Mon Sep 17 00:00:00 2001 From: RaspberryPie Date: Mon, 14 Oct 2013 17:49:06 +0000 Subject: [PATCH] Added a comment --- .../comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/git-annex:_status:_1_failed/comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment diff --git a/doc/forum/git-annex:_status:_1_failed/comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment b/doc/forum/git-annex:_status:_1_failed/comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment new file mode 100644 index 0000000000..e4fae1f312 --- /dev/null +++ b/doc/forum/git-annex:_status:_1_failed/comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="RaspberryPie" + ip="204.8.156.142" + subject="comment 8" + date="2013-10-14T17:49:05Z" + content=""" +Quick question: Is there any way to get rid of the error in the existing repository (e.g. remove the problematic tmp file entry) so I can get a complete status output? Bonus points if I don't have to annex every single file anew. `git annex fsck` doesn't work, as doesn't `git annex fix` (it's a direct repo). +"""]]