From 106373c53b5e725c8d14f145c1fa338b850e19d0 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 10 Mar 2025 16:46:55 -0400 Subject: [PATCH] response --- ...ment_2_53493ef08c5cef81c6b6ae64afc47c07._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/special_remotes/compute/comment_2_53493ef08c5cef81c6b6ae64afc47c07._comment diff --git a/doc/special_remotes/compute/comment_2_53493ef08c5cef81c6b6ae64afc47c07._comment b/doc/special_remotes/compute/comment_2_53493ef08c5cef81c6b6ae64afc47c07._comment new file mode 100644 index 0000000000..ef6def3f4e --- /dev/null +++ b/doc/special_remotes/compute/comment_2_53493ef08c5cef81c6b6ae64afc47c07._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""Re: Any way to annotate what are input files?""" + date="2025-03-10T20:42:26Z" + content=""" +git-annex does know what both the input and the output files are. +It learns this by running the compute program and seeing what INPUT and OUTPUT +lines it emits. + +I considered having some `--input=` option, but decided that it was more +flexible to have a more freeform command line, which the compute program +parses. +"""]]