summaryrefslogtreecommitdiffstats
path: root/gitprotocol-v2.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2023-01-16 13:19:04 -0800
committerJunio C Hamano <gitster@pobox.com>2023-01-16 13:19:04 -0800
commitd2309374057e387bf3b3f77ed51de90c6f1af162 (patch)
treea15f0f4e987a56b325efb7dc0ab40794bd0ee777 /gitprotocol-v2.html
parent7657f149df9d40ac2a9193b88f2e7f0b7c9dc532 (diff)
downloadgit-htmldocs-d2309374057e387bf3b3f77ed51de90c6f1af162.tar.gz
Autogenerated HTML docs for v2.39.0-227-g262c45
Diffstat (limited to 'gitprotocol-v2.html')
-rw-r--r--gitprotocol-v2.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/gitprotocol-v2.html b/gitprotocol-v2.html
index a49b2fbaf..fcc493150 100644
--- a/gitprotocol-v2.html
+++ b/gitprotocol-v2.html
@@ -1566,7 +1566,7 @@ headers and their prerequisite relationships, or something else.
</p>
<div class="paragraph"><p>Server operators should feel confident in turning on "bundle-uri" and
not worry if e.g. their CDN goes down that clones or fetches will run
-into hard failures. Even if the server bundle bundle(s) are
+into hard failures. Even if the server bundle(s) are
incomplete, or bad in some way the client should still end up with a
functioning repository, just as if it had chosen not to use this
protocol extension.</p></div>
@@ -1719,7 +1719,7 @@ headers of that bundle or bundles.</p></div>
<div id="footer">
<div id="footer-text">
Last updated
- 2023-01-02 22:37:31 JST
+ 2023-01-16 13:16:56 PST
</div>
</div>
</body>