From 32df7fca23407af74664440f64a8019c30b0c50f Mon Sep 17 00:00:00 2001 From: "uli@8484a70fbfd489faef5f72c230d340b01e2676ca" Date: Wed, 11 Jul 2018 14:07:24 +0000 Subject: [PATCH] --- ..._other_repositories_should_not_need_a_git_remote.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/todo/Finding_content_in_other_repositories_should_not_need_a_git_remote.mdwn diff --git a/doc/todo/Finding_content_in_other_repositories_should_not_need_a_git_remote.mdwn b/doc/todo/Finding_content_in_other_repositories_should_not_need_a_git_remote.mdwn new file mode 100644 index 0000000000..52d2ef08c6 --- /dev/null +++ b/doc/todo/Finding_content_in_other_repositories_should_not_need_a_git_remote.mdwn @@ -0,0 +1,9 @@ +git annex unused supports an --from option to select a specific remote to find unused data in. When you use that on a repository which is not linked to from the current repository by a git remote, git annex fails: + + $ git annex unused --from somerepository + git-annex: there is no available git remote named somerepository + $ git annex unused --from repowithremote + unused repowithremote (checking for unused data...) + [...] + +As git annex at least for newly-deleted files knows when those are stored in the given repository, git annex should at least find those.