summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2021-02-03 15:04:49 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-02-03 15:04:49 -0800
commitd03553ecd135b32da1c68ffb3190e4efbb616a26 (patch)
treeccf6d9fb3abd1a235ad849d87a667af39b4369e6
parentMerge branch 'ds/maintenance-prefetch-cleanup' (diff)
parentDoc: clarify contents of packfile sent as URI (diff)
downloadtgif-d03553ecd135b32da1c68ffb3190e4efbb616a26.tar.xz
Merge branch 'jt/packfile-as-uri-doc'
Doc fix for packfile URI feature. * jt/packfile-as-uri-doc: Doc: clarify contents of packfile sent as URI
-rw-r--r--Documentation/technical/packfile-uri.txt7
1 files changed, 5 insertions, 2 deletions
diff --git a/Documentation/technical/packfile-uri.txt b/Documentation/technical/packfile-uri.txt
index 318713abc3..f7eabc6c76 100644
--- a/Documentation/technical/packfile-uri.txt
+++ b/Documentation/technical/packfile-uri.txt
@@ -37,8 +37,11 @@ at least so that we can test the client.
This is the implementation: a feature, marked experimental, that allows the
server to be configured by one or more `uploadpack.blobPackfileUri=<sha1>
<uri>` entries. Whenever the list of objects to be sent is assembled, all such
-blobs are excluded, replaced with URIs. The client will download those URIs,
-expecting them to each point to packfiles containing single blobs.
+blobs are excluded, replaced with URIs. As noted in "Future work" below, the
+server can evolve in the future to support excluding other objects (or other
+implementations of servers could be made that support excluding other objects)
+without needing a protocol change, so clients should not expect that packfiles
+downloaded in this way only contain single blobs.
Client design
-------------