From ebaedbd1753fcb3d34ddaec9f1d04a1f70fcdf7c Mon Sep 17 00:00:00 2001 From: NorsePaladin Date: Sat, 7 Jun 2025 03:21:24 +0000 Subject: [PATCH] Special remote protocol: How to identify exact size of a particular key? --- ...ecial_remote_protocol__58___How_to_identify_exactsize.mdwn | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 doc/forum/special_remote_protocol__58___How_to_identify_exactsize.mdwn diff --git a/doc/forum/special_remote_protocol__58___How_to_identify_exactsize.mdwn b/doc/forum/special_remote_protocol__58___How_to_identify_exactsize.mdwn new file mode 100644 index 0000000000..472d69d1f9 --- /dev/null +++ b/doc/forum/special_remote_protocol__58___How_to_identify_exactsize.mdwn @@ -0,0 +1,4 @@ +I'm trying to write a special remote protocol in which it would be really helpful to have the exact size for a particular key. I was thinking of something like the special remote asking git-annex `GETKEYINFO ` and git annex responds with some useful info (Something like a dictionary of useful values maybe?) + +I considered doing something like `git annex info ..` to figure this out but realized it's a bad idea(That'll be very brittle, plus it won't work well with chunked/encrypted remotes at all). Does git annex typically have this info available? It would even be helpful if it only gives responses in specific cases (eg: no encryption since it'll presumably be hard to keep track of that case) +