From: Joey Hess Date: Mon, 22 Sep 2025 15:10:32 +0000 (-0400) Subject: comment X-Git-Tag: archive/raspbian/10.20251029-1+rpi1~1^2~3^2~82 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=6fa46c644370f89f40f44634aa9c29c374c54d20;p=git-annex.git comment --- diff --git a/doc/design/external_special_remote_protocol/comment_56_1d600b1ed8ba2c563b8bc753d224ea05._comment b/doc/design/external_special_remote_protocol/comment_56_1d600b1ed8ba2c563b8bc753d224ea05._comment new file mode 100644 index 0000000000..01a4ade4ee --- /dev/null +++ b/doc/design/external_special_remote_protocol/comment_56_1d600b1ed8ba2c563b8bc753d224ea05._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""Re: support for bulk write/read/test remote""" + date="2025-09-22T15:02:49Z" + content=""" +@psxvoid that's fundamentally different than how git-annex works, so there +will need to be some kind of translation layer. And I think you could put +it in your special remote. + +For example, you could store both the archive file, as well as annex object +files that have not yet made it into the archive. So that when git-annex +sends a file to your remote, the file is actually stored in the remote, +rather than in a temporary location. Then you could periodically make a +new archive file from the loose objects. +"""]]