From: "TimTIM via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: TimTIM <t2@live.hk>, TimTim Wong <t2@live.hk>
Subject: [PATCH] http-protocol.txt: add missing flush to example
Date: Thu, 18 Nov 2021 11:16:43 +0000 [thread overview]
Message-ID: <pull.1141.git.git.1637234203401.gitgitgadget@gmail.com> (raw)
From: TimTim Wong <t2@live.hk>
Signed-off-by: Timothy Wong <i@timtim.hk>
---
Fix example in documentation
wants must be flushed with 0000 before haves
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1141%2Fwegylexy%2Fpatch-1-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1141/wegylexy/patch-1-v1
Pull-Request: https://github.com/git/git/pull/1141
Documentation/technical/http-protocol.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/technical/http-protocol.txt b/Documentation/technical/http-protocol.txt
index cc5126cfeda..facb315a993 100644
--- a/Documentation/technical/http-protocol.txt
+++ b/Documentation/technical/http-protocol.txt
@@ -314,8 +314,9 @@ Clients MUST first perform ref discovery with
C: Content-Type: application/x-git-upload-pack-request
C:
C: 0032want 0a53e9ddeaddad63ad106860237bbf53411d11a7\n
- C: 0032have 441b40d833fdfa93eb2908e52742248faf0ee993\n
C: 0000
+ C: 0032have 441b40d833fdfa93eb2908e52742248faf0ee993\n
+ C: done
S: 200 OK
S: Content-Type: application/x-git-upload-pack-result
@@ -337,9 +338,9 @@ server advertises capability `allow-tip-sha1-in-want` or
`allow-reachable-sha1-in-want`.
compute_request = want_list
+ "0000"
have_list
- request_end
- request_end = "0000" / "done"
+ "done"
want_list = PKT-LINE(want SP cap_list LF)
*(want_pkt)
base-commit: cd3e606211bb1cf8bc57f7d76bab98cc17a150bc
--
gitgitgadget
next reply other threads:[~2021-11-18 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 11:16 TimTIM via GitGitGadget [this message]
2021-11-18 16:38 ` [PATCH] http-protocol.txt: add missing flush to example Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.1141.git.git.1637234203401.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=t2@live.hk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.