From 67034a02ea3898305643763665ae3db8a4a781d2 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 28 Jan 2025 11:38:04 -0400 Subject: [PATCH] update --- .../comment_10_304b925c5c54b1fd980446920780be00._comment | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/todo/compute_special_remote/comment_10_304b925c5c54b1fd980446920780be00._comment b/doc/todo/compute_special_remote/comment_10_304b925c5c54b1fd980446920780be00._comment index 73249ac05c..0a870654f6 100644 --- a/doc/todo/compute_special_remote/comment_10_304b925c5c54b1fd980446920780be00._comment +++ b/doc/todo/compute_special_remote/comment_10_304b925c5c54b1fd980446920780be00._comment @@ -58,12 +58,13 @@ Also, that command could let input values be adjusted later: git commit -m 'include the introduction of the speaker in the clip' It would also be good to have a command that examines a computed key -and displays the values and inputs. Eg: +and displays the values and inputs. That could be `git-annex whereis` +or perhaps a dedicated command with more structured output: git-annex examinecompute foo --from ffmpeg-cut source=input.mov (annex key SHA256--xxxxxxxxx) starttime=15:00 endtime=30:00 -This feels like it might allow for some useful workflows... +This all feels like it might allow for some useful workflows... """]]