docs/protocol-v2: point readers transport config discussion
We recently added tips for server admins to configure various transports to support v2's GIT_PROTOCOL variable. While the protocol-v2 document is pretty technical and not of interest to most admins, it may be a starting point for them to figure out how to turn on v2. Let's put some pointers from there to the other documentation. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jeff King committed
Sep 10, 2021 at 10:10 UTC
1b421e7a5aa6984777029ab799f9a0221875e1dd
1 file changed
+7
-1
Documentation/technical/protocol-v2.txt
+7
-1
@@ -42,7 +42,8 @@ Initial Client Request
42
In general a client can request to speak protocol v2 by sending
43
`version=2` through the respective side-channel for the transport being
44
used which inevitably sets `GIT_PROTOCOL`. More information can be
45
-found in `pack-protocol.txt` and `http-protocol.txt`. In all cases the
45
+found in `pack-protocol.txt` and `http-protocol.txt`, as well as the
46
+`GIT_PROTOCOL` definition in `git.txt`. In all cases the
47
response from the server is the capability advertisement.
48
49
Git Transport
@@ -58,6 +59,8 @@ SSH and File Transport
59
60
When using either the ssh:// or file:// transport, the GIT_PROTOCOL
61
environment variable must be set explicitly to include "version=2".
62
+The server may need to be configured to allow this environment variable
63
+to pass.
64
65
HTTP Transport
66
~~~~~~~~~~~~~~
@@ -81,6 +84,9 @@ A v2 server would reply:
84
Subsequent requests are then made directly to the service
85
`$GIT_URL/git-upload-pack`. (This works the same for git-receive-pack).
86
87
+The server may need to be configured to pass this header's contents via
88
+the `GIT_PROTOCOL` variable. See the discussion in `git-http-backend.txt`.
89
+
90
Capability Advertisement
91
------------------------
92