From 5d407aa5a437f63971096d6951ddb928949da2ca Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 4 May 2020 12:55:41 -0400 Subject: [PATCH] response --- ...nt_1_a1827481a3ac140d58a4184121328d87._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/Best_way_to_extract_git-annex_object_files___40__with_correct_names__41___in_absence_of_git_log/comment_1_a1827481a3ac140d58a4184121328d87._comment diff --git a/doc/forum/Best_way_to_extract_git-annex_object_files___40__with_correct_names__41___in_absence_of_git_log/comment_1_a1827481a3ac140d58a4184121328d87._comment b/doc/forum/Best_way_to_extract_git-annex_object_files___40__with_correct_names__41___in_absence_of_git_log/comment_1_a1827481a3ac140d58a4184121328d87._comment new file mode 100644 index 0000000000..770fed4425 --- /dev/null +++ b/doc/forum/Best_way_to_extract_git-annex_object_files___40__with_correct_names__41___in_absence_of_git_log/comment_1_a1827481a3ac140d58a4184121328d87._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2020-05-04T16:50:59Z" + content=""" +By "git log", are you talking about the actual git history of the +repository? + +If this repository is a clone from some other repository, then +`git annex repair` may be able to help, by repairing the git repository +damage with information from the other repository. + +The git repository is where the names of files are stored, so if you manage +to completely lose that information, you're kind of out of luck. +"""]]