From 96b549779a6550e5bbd75d56c1237615041dcdba Mon Sep 17 00:00:00 2001 From: meribold Date: Fri, 12 Mar 2021 03:58:08 +0000 Subject: [PATCH] Added a comment --- ...mment_2_d0aa8cc29e38510b2bb1c4ce356aa2ac._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/todo/git-annex-unused_--history/comment_2_d0aa8cc29e38510b2bb1c4ce356aa2ac._comment diff --git a/doc/todo/git-annex-unused_--history/comment_2_d0aa8cc29e38510b2bb1c4ce356aa2ac._comment b/doc/todo/git-annex-unused_--history/comment_2_d0aa8cc29e38510b2bb1c4ce356aa2ac._comment new file mode 100644 index 0000000000..f4f7be7b50 --- /dev/null +++ b/doc/todo/git-annex-unused_--history/comment_2_d0aa8cc29e38510b2bb1c4ce356aa2ac._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="meribold" + avatar="http://cdn.libravatar.org/avatar/8cfdfc37c8459a7320aa6bb9f2689112" + subject="comment 2" + date="2021-03-12T03:58:03Z" + content=""" +Another name for a `git-annex unused` switch could be `--unreachable`. I suppose `git-annex gc` would drop unreachable files without a separate `git-annex dropunused` invocation? That would work for me as well. + +> I wonder if someone might want to keep all versions of files from one branch, but only the current version of another branch? + +Personally I don't have the use case of `git-annex unused` only looking at the history of some refs and treating other refs normally. +"""]]