decided to leave message as-is
"getting input <file> from <remote>" is talking about the original input filename. I think that's ok.
This commit is contained in:
parent
f835919e40
commit
85fe283c05
1 changed files with 0 additions and 5 deletions
|
@ -21,11 +21,6 @@ compute special remote. --[[Joey]]
|
||||||
what files are inputs for another file. Or it could be exposed in the
|
what files are inputs for another file. Or it could be exposed in the
|
||||||
Remote interface, and made into a file matching option.
|
Remote interface, and made into a file matching option.
|
||||||
|
|
||||||
* "getting input from <file>" message uses the original filename,
|
|
||||||
but that file might have been renamed. Would be more clear to use
|
|
||||||
whatever file in the tree currently points to the key it's getting
|
|
||||||
(what if there is not one?)
|
|
||||||
|
|
||||||
* allow git-annex enableremote with program= explicitly specified,
|
* allow git-annex enableremote with program= explicitly specified,
|
||||||
without checking annex.security.allowed-compute-programs
|
without checking annex.security.allowed-compute-programs
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue