summaryrefslogtreecommitdiffstats
path: root/gitprotocol-v2.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2024-02-08 15:48:36 -0800
committerJunio C Hamano <gitster@pobox.com>2024-02-08 15:48:36 -0800
commit6546a509a43eda541b7749ee45837d7a74ba7339 (patch)
treea4753bbbeb6fa8a064cbcf570aadb5d4354a1ceb /gitprotocol-v2.txt
parentc2015e3db30c76ee24b99a14d244f62f1467f581 (diff)
downloadgit-htmldocs-6546a509a43eda541b7749ee45837d7a74ba7339.tar.gz
Autogenerated HTML docs for v2.43.0-581-g5216f
Diffstat (limited to 'gitprotocol-v2.txt')
-rw-r--r--gitprotocol-v2.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/gitprotocol-v2.txt b/gitprotocol-v2.txt
index 8c1e7c61e..0b800abd5 100644
--- a/gitprotocol-v2.txt
+++ b/gitprotocol-v2.txt
@@ -199,7 +199,7 @@ which can be used to limit the refs sent from the server.
Additional features not supported in the base command will be advertised
as the value of the command in the capability advertisement in the form
-of a space separated list of features: "<command>=<feature 1> <feature 2>"
+of a space separated list of features: "<command>=<feature-1> <feature-2>"
ls-refs takes in the following arguments:
@@ -245,7 +245,7 @@ addition of future extensions.
Additional features not supported in the base command will be advertised
as the value of the command in the capability advertisement in the form
-of a space separated list of features: "<command>=<feature 1> <feature 2>"
+of a space separated list of features: "<command>=<feature-1> <feature-2>"
A `fetch` request can take the following arguments:
@@ -363,7 +363,7 @@ can be included in the client's request as well as the potential
addition of the 'packfile-uris' section in the server's response as
explained below.
- packfile-uris <comma-separated list of protocols>
+ packfile-uris <comma-separated-list-of-protocols>
Indicates to the server that the client is willing to receive
URIs of any of the given protocols in place of objects in the
sent packfile. Before performing the connectivity check, the
@@ -534,7 +534,7 @@ with objects using hash algorithm X. If not specified, the server is assumed to
only handle SHA-1. If the client would like to use a hash algorithm other than
SHA-1, it should specify its object-format string.
-session-id=<session id>
+session-id=<session-id>
~~~~~~~~~~~~~~~~~~~~~~~
The server may advertise a session ID that can be used to identify this process