From 522d032016ec3a35d2a378585f55f39141a735c6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 5 Jul 2023 17:20:47 -0400 Subject: [PATCH] comment --- ...ent_1_bcb54e40904b04006dd7f8962add6994._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/todo/Adding_a_matcher_for___39__recently_touched_files__39__/comment_1_bcb54e40904b04006dd7f8962add6994._comment diff --git a/doc/todo/Adding_a_matcher_for___39__recently_touched_files__39__/comment_1_bcb54e40904b04006dd7f8962add6994._comment b/doc/todo/Adding_a_matcher_for___39__recently_touched_files__39__/comment_1_bcb54e40904b04006dd7f8962add6994._comment new file mode 100644 index 0000000000..4848b5b191 --- /dev/null +++ b/doc/todo/Adding_a_matcher_for___39__recently_touched_files__39__/comment_1_bcb54e40904b04006dd7f8962add6994._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2023-07-05T21:12:07Z" + content=""" +There's a plan for [[speeding up sync --content|todo/Incremental_git_annex_sync_--content_--all]] (and `assist`). + +That method is farly similar, and it wouldn't need the user to specify +an additional matching option to get the speedup. + +I do think this could be a useful option to have though. (It would not be +possible to implement it as a matcher, but that's an implementation +detail.) +"""]] -- 2.30.2