response
authorJoey Hess <joeyh@joeyh.name>
Mon, 10 Mar 2025 20:46:55 +0000 (16:46 -0400)
committerJoey Hess <joeyh@joeyh.name>
Mon, 10 Mar 2025 20:46:55 +0000 (16:46 -0400)
doc/special_remotes/compute/comment_2_53493ef08c5cef81c6b6ae64afc47c07._comment [new file with mode: 0644]

diff --git a/doc/special_remotes/compute/comment_2_53493ef08c5cef81c6b6ae64afc47c07._comment b/doc/special_remotes/compute/comment_2_53493ef08c5cef81c6b6ae64afc47c07._comment
new file mode 100644 (file)
index 0000000..ef6def3
--- /dev/null
@@ -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.
+"""]]