From a766475d14c0488206afd9b82dce1b0a95d8eaf3 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 27 May 2024 12:50:46 -0400 Subject: [PATCH] split out a todo --- doc/todo/git-remote-annex.mdwn | 6 +---- ...mote-annex_web_special_remote_support.mdwn | 23 +++++++++++++++++++ 2 files changed, 24 insertions(+), 5 deletions(-) create mode 100644 doc/todo/git-remote-annex_web_special_remote_support.mdwn diff --git a/doc/todo/git-remote-annex.mdwn b/doc/todo/git-remote-annex.mdwn index 09708814c5..269cf0772b 100644 --- a/doc/todo/git-remote-annex.mdwn +++ b/doc/todo/git-remote-annex.mdwn @@ -15,8 +15,4 @@ This is implememented and working. Remaining todo list for it: not display any useful error message. git fetch does, but it seems git clone eats git-remote-annex stderr. -* datalad-annex supports cloning from the web special remote, - using an url that contains the result of pushing to eg, a directory - special remote. - `datalad-annex::https://example.com?type=web&url={noquery}` - Supporting something like this would be good. +See also: [[git-remote-annex_web_special_remote_support]] diff --git a/doc/todo/git-remote-annex_web_special_remote_support.mdwn b/doc/todo/git-remote-annex_web_special_remote_support.mdwn new file mode 100644 index 0000000000..f31b41646b --- /dev/null +++ b/doc/todo/git-remote-annex_web_special_remote_support.mdwn @@ -0,0 +1,23 @@ +datalad-annex supports cloning from the web special remote, +using an url that contains the result of pushing to eg, a directory +special remote. + +`datalad-annex::https://example.com?type=web&url={noquery}` + +Supporting something like this in git-remote-annex would be good. + +While to the user this might be considered part of the web special remote, +it would really be a separate download code path in git-remote-annex that +downloads from the urls. + +datalad-annex assumes that the url uses the exporttree=yes layout. +If git-annex did the same, it would look in "$url/.git/annex/objects/". +But it could instead try both that and the regular hash directories +and use whichever it found. + +How should the annex:: url look for this? The UUID is not really relevant +in this case, because the web only has a dummy single UUID. So +it would work to use "annex::https://example.com/?type=web" + +What should be recorded in .git/config for such a remote? I suppose the +annex:: url and no annex-uuid. --[[Joey]]