From 0dc5af8d6c96cf80967b2b144edfd03624a8faa7 Mon Sep 17 00:00:00 2001 From: Marco Date: Fri, 15 May 2015 08:01:25 +0000 Subject: Added a comment: git annex repair --force --- .../comment_1_0dfd9eedccb48f1f3d7939677dc96446._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_1_0dfd9eedccb48f1f3d7939677dc96446._comment (limited to 'doc/bugs') diff --git a/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_1_0dfd9eedccb48f1f3d7939677dc96446._comment b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_1_0dfd9eedccb48f1f3d7939677dc96446._comment new file mode 100644 index 000000000..be48ca87f --- /dev/null +++ b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_1_0dfd9eedccb48f1f3d7939677dc96446._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="Marco" + subject="git annex repair --force" + date="2015-05-15T08:01:25Z" + content=""" +This command removed all history. It looks like no file was ever added. + +Any idea how I should handle this client repository? I could clone again from a backup. Is it possible to keep the annex UUID for a new clone? +"""]] -- cgit v1.2.3