From d36de3edf95e208b74bb02b4cc704a06c2db4958 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 21 Feb 2022 12:49:36 -0400 Subject: [PATCH] comment --- ..._1_3b96becda1db6ae23adb5077b6332718._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/todo/info__58___allow_file_matching_options_for_all_keys/comment_1_3b96becda1db6ae23adb5077b6332718._comment diff --git a/doc/todo/info__58___allow_file_matching_options_for_all_keys/comment_1_3b96becda1db6ae23adb5077b6332718._comment b/doc/todo/info__58___allow_file_matching_options_for_all_keys/comment_1_3b96becda1db6ae23adb5077b6332718._comment new file mode 100644 index 0000000000..526501622b --- /dev/null +++ b/doc/todo/info__58___allow_file_matching_options_for_all_keys/comment_1_3b96becda1db6ae23adb5077b6332718._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-02-21T16:19:27Z" + content=""" +You can use: `git-annex info . --in here` + +But, it should be possible when getting info for all keys +to use the matching options like --in that do not match on a filename. +It used to be that there was no way to tell which kind of matching options +where used, but now `matchNeedsFileName` is available and it could only +reject those. + +So this can be implemented by making cachedPresentData +and cachedRemoteData get the matcher, check if it's +the right kind and apply it to the keys. +"""]]