From 6b837d17c29e1f72a94fe5a43bb2f5560f6fba66 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Tue, 26 Mar 2024 19:13:15 +0000 Subject: [PATCH] Added a comment --- .../comment_1_8bb17f1a8297b500dcc5bdf9412a5d6c._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/external_special_remotes_not_using_git-annex-remote_in_name/comment_1_8bb17f1a8297b500dcc5bdf9412a5d6c._comment diff --git a/doc/todo/external_special_remotes_not_using_git-annex-remote_in_name/comment_1_8bb17f1a8297b500dcc5bdf9412a5d6c._comment b/doc/todo/external_special_remotes_not_using_git-annex-remote_in_name/comment_1_8bb17f1a8297b500dcc5bdf9412a5d6c._comment new file mode 100644 index 0000000000..e5e87eaf0b --- /dev/null +++ b/doc/todo/external_special_remotes_not_using_git-annex-remote_in_name/comment_1_8bb17f1a8297b500dcc5bdf9412a5d6c._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 1" + date="2024-03-26T19:13:15Z" + content=""" +my 1c: since `git-annex` is pretty much following git's own `git-remote-` paradigm here, I think it is ok to require `git-annex-remote-` to even simply be able to check what are the available `git-annex` remotes etc. Providing a shim to pass through to some tool specific interface is IMHO trivial enough. And as you outline, such approach also helps to avoid a security concern. +"""]]