summaryrefslogtreecommitdiffstats
path: root/gitprotocol-http.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2023-10-23 14:45:54 -0700
committerJunio C Hamano <gitster@pobox.com>2023-10-23 14:45:54 -0700
commit33be82183d4cd6dc645f64da1402cf9a3f4cdbf3 (patch)
tree4a681cad5c6da23a7d7f56022666fb31397026d2 /gitprotocol-http.html
parent359f02427091f2c0fcac4eb7651fe5d159b84a54 (diff)
downloadgit-htmldocs-33be82183d4cd6dc645f64da1402cf9a3f4cdbf3.tar.gz
Autogenerated HTML docs for v2.42.0-482-g2e8e7
Diffstat (limited to 'gitprotocol-http.html')
-rw-r--r--gitprotocol-http.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/gitprotocol-http.html b/gitprotocol-http.html
index 62f55c8f2..0285551f6 100644
--- a/gitprotocol-http.html
+++ b/gitprotocol-http.html
@@ -782,7 +782,7 @@ the http:// repository URL entered by the end-user.</p></div>
both the "smart" and "dumb" HTTP protocols used by Git operate
by appending additional path components onto the end of the user
supplied <code>$GIT_URL</code> string.</p></div>
-<div class="paragraph"><p>An example of a dumb client requesting for a loose object:</p></div>
+<div class="paragraph"><p>An example of a dumb client requesting a loose object:</p></div>
<div class="literalblock">
<div class="content">
<pre><code>$GIT_URL: http://example.com:8080/git/repo.git
@@ -1109,7 +1109,7 @@ cap_list = capability *(SP capability)</code></pre>
<div class="paragraph"><p>C: Place any object seen into set <code>advertised</code>.</p></div>
<div class="paragraph"><p>C: Build an empty set, <code>common</code>, to hold the objects that are later
determined to be on both ends.</p></div>
-<div class="paragraph"><p>C: Build a set, <code>want</code>, of the objects from <code>advertised</code> the client
+<div class="paragraph"><p>C: Build a set, <code>want</code>, of the objects from <code>advertised</code> that the client
wants to fetch, based on what it saw during ref discovery.</p></div>
<div class="paragraph"><p>C: Start a queue, <code>c_pending</code>, ordered by commit time (popping newest
first). Add all client refs. When a commit is popped from
@@ -1156,7 +1156,7 @@ object name as its value. Multiple object names MUST be sent by sending
multiple commands. Object names MUST be given using the object format
negotiated through the <code>object-format</code> capability (default SHA-1).</p></div>
<div class="paragraph"><p>The <code>have</code> list is created by popping the first 32 commits
-from <code>c_pending</code>. Less can be supplied if <code>c_pending</code> empties.</p></div>
+from <code>c_pending</code>. Fewer can be supplied if <code>c_pending</code> empties.</p></div>
<div class="paragraph"><p>If the client has sent 256 "have" commits and has not yet
received one of those back from <code>s_common</code>, or the client has
emptied <code>c_pending</code> it SHOULD include a "done" command to let
@@ -1279,7 +1279,7 @@ update = old_id SP new_id SP name</code></pre>
<div id="footer">
<div id="footer-text">
Last updated
- 2022-08-18 14:11:07 PDT
+ 2023-10-23 14:43:46 PDT
</div>
</div>
</body>