diff options
author | eigengrau <eigengrau@web> | 2015-05-28 13:44:32 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2015-05-28 13:44:32 +0000 |
commit | 56d65a425c9461c88587d070cc732dc49a1d674f (patch) | |
tree | 3d845862eae89a17930affa446dfc803a625adea | |
parent | fabd07e5ff083b8fc99de47d8162ab0e1ca2d9a6 (diff) |
Added a comment
-rw-r--r-- | doc/todo/find_unused_in_any_commit/comment_2_ab373440bf7bab9179fdfccf6da3e8a4._comment | 7 |
1 files changed, 7 insertions, 0 deletions
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. +"""]] |