From 56d65a425c9461c88587d070cc732dc49a1d674f Mon Sep 17 00:00:00 2001 From: eigengrau Date: Thu, 28 May 2015 13:44:32 +0000 Subject: Added a comment --- .../comment_2_ab373440bf7bab9179fdfccf6da3e8a4._comment | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/todo/find_unused_in_any_commit/comment_2_ab373440bf7bab9179fdfccf6da3e8a4._comment diff --git a/doc/todo/find_unused_in_any_commit/comment_2_ab373440bf7bab9179fdfccf6da3e8a4._comment b/doc/todo/find_unused_in_any_commit/comment_2_ab373440bf7bab9179fdfccf6da3e8a4._comment new file mode 100644 index 000000000..8d489927f --- /dev/null +++ b/doc/todo/find_unused_in_any_commit/comment_2_ab373440bf7bab9179fdfccf6da3e8a4._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="eigengrau" + subject="comment 2" + date="2015-05-28T13:44:32Z" + content=""" +This would be absolutely awesome, because it would pruning away old data based on cut-offs. One could squash all history beyond some cut-off point. Or, probably better, one could preserve git history, but supply “git annex fsck” with a cut-off switch that specifies a date or time interval. All data referred to in commits older than the specified interval is then considered unused. +"""]] -- cgit v1.2.3