diff options
author | yarikoptic <yarikoptic@web> | 2018-02-05 15:53:06 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2018-02-05 15:53:06 +0000 |
commit | f9988a6abaf7980b4e699086a65dc52b540d39fa (patch) | |
tree | 9740a8d992b4464e7e834c918f632b4678e34de5 | |
parent | 2f2f255e89cae0c1d60f3565d316baa94f947a3a (diff) |
initial report
-rw-r--r-- | doc/todo/INFO_message_for_custom_special_remotes.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/todo/INFO_message_for_custom_special_remotes.mdwn b/doc/todo/INFO_message_for_custom_special_remotes.mdwn new file mode 100644 index 000000000..b41ea89bc --- /dev/null +++ b/doc/todo/INFO_message_for_custom_special_remotes.mdwn @@ -0,0 +1,3 @@ +I wondered if it would be sensible to ask to extend [externals special remote protocol](https://git-annex.branchable.com/design/external_special_remote_protocol/) with ability for custom remotes to pass back some INFO level message (not only DEBUG or ERROR). The reason is: in datalad-archives special remote we usually need to `git annex get` first the key containing the archive, which might be sizeable. Since there is ATM no way to communicate back to git-annex, so it could communicate back to the datalad which runs it, it results in no output/message to the user that possibly a heavy download is happening in the background. So, we would need to establish our own communication from datalad-archives special remote all the way to top level datalad process to report that, or I wondered if may be we could report back to git-annex, and it in turn report back to the original process (running e.g. `annex get --json --json-progress`) so it could spit out that message wrapped into a json record within the stream, so we could process and output that to the user. + +[[!meta author=yoh]] |