From 93be470d2c2c83b5cbda5b3258c971e6a425551c Mon Sep 17 00:00:00 2001 From: "basile.pinsard@f1a7fae9f3bd9d5282fca11f62ad53b45a8eb317" Date: Fri, 22 May 2020 13:24:19 +0000 Subject: [PATCH] Added a comment --- ...nt_4_577f586843c1d7e54d115796988f912d._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/How_do_I_revert_back_to_specific_commit_with_git_annex/comment_4_577f586843c1d7e54d115796988f912d._comment diff --git a/doc/forum/How_do_I_revert_back_to_specific_commit_with_git_annex/comment_4_577f586843c1d7e54d115796988f912d._comment b/doc/forum/How_do_I_revert_back_to_specific_commit_with_git_annex/comment_4_577f586843c1d7e54d115796988f912d._comment new file mode 100644 index 0000000000..3200ca1dad --- /dev/null +++ b/doc/forum/How_do_I_revert_back_to_specific_commit_with_git_annex/comment_4_577f586843c1d7e54d115796988f912d._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="basile.pinsard@f1a7fae9f3bd9d5282fca11f62ad53b45a8eb317" + nickname="basile.pinsard" + avatar="http://cdn.libravatar.org/avatar/87e1f73acf277ad0337b90fc0253c62e" + subject="comment 4" + date="2020-05-22T13:24:19Z" + content=""" +Thanks for the detailed answer. + +So the only way to revert metadata changes is to reset the git-annex branch to a previous commit with `git update-ref refs/heads/git-annex `. + +Thanks for the `git-log --stat` tip. + +I guess I could get an approximate match between the master and git-annex branches commits based on commit date. +"""]]