From 664c15f20af9e33dc71586a3461e3f61c44b97af Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 15 Feb 2021 13:31:13 -0400 Subject: [PATCH] comment --- ...t_5_022728be6cd3ac168a74d16baf29c0e1._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/Reverse_index_key_to_list_of_file_paths/comment_5_022728be6cd3ac168a74d16baf29c0e1._comment diff --git a/doc/forum/Reverse_index_key_to_list_of_file_paths/comment_5_022728be6cd3ac168a74d16baf29c0e1._comment b/doc/forum/Reverse_index_key_to_list_of_file_paths/comment_5_022728be6cd3ac168a74d16baf29c0e1._comment new file mode 100644 index 0000000000..5895b8bc71 --- /dev/null +++ b/doc/forum/Reverse_index_key_to_list_of_file_paths/comment_5_022728be6cd3ac168a74d16baf29c0e1._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2021-02-15T17:25:05Z" + content=""" +git grep doesn't use an index per se, but is probably faster +than `find` at least sometimes. And probably somewhat faster than things +involving `git-annex find` too. + +It's unfortunate that `git grep` doesn't search on the content of symlink +texts, so that can't be used to find locked files. + +The equivilant using git-annex find, which will find both types: + + git annex find --format '${key}\n' | grep SHA256E-s320029--488e29f5584ba4e474db95aa42fbb58ddb92f2a59bc0b24a91171acb4d8f4828.png +"""]]