From 9943440a479a53c17bfda42ab8efa301b89e6b83 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 22 May 2015 13:18:30 -0400 Subject: comment --- .../comment_1_2b34b39ef76f205187b1d44fbbccd7f6._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget/comment_1_2b34b39ef76f205187b1d44fbbccd7f6._comment diff --git a/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget/comment_1_2b34b39ef76f205187b1d44fbbccd7f6._comment b/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget/comment_1_2b34b39ef76f205187b1d44fbbccd7f6._comment new file mode 100644 index 000000000..e5f50c84a --- /dev/null +++ b/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget/comment_1_2b34b39ef76f205187b1d44fbbccd7f6._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-05-22T17:16:28Z" + content=""" +`git annex forget` removes historcal data about where files were located in +the past, but it does not affect the current logs about the current +location (or lack of location) of files. + +It would be possible to extend `git annex forget` to do that, which is one +approach to possibly solving [[fsck_reports_unsolvable_problem]]. +"""]] -- cgit v1.2.3