From: "Heath Dutton🕴️ via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: jrnieder@gmail.com, "Heath Dutton🕴️" <heathdutton@gmail.com>,
"Heath Dutton🕴️" <heathdutton@gmail.com>
Subject: [PATCH] doc: define timestamp in pack protocol grammar
Date: Sun, 04 Jan 2026 03:08:40 +0000 [thread overview]
Message-ID: <pull.2154.git.git.1767496120852.gitgitgadget@gmail.com> (raw)
From: =?UTF-8?q?Heath=20Dutton=F0=9F=95=B4=EF=B8=8F?=
<heathdutton@gmail.com>
The grammar for depth-request uses 'timestamp' but never defines it,
unlike 'depth' which is properly defined as '1*DIGIT'. Add the missing
definition.
Signed-off-by: Heath Dutton <heathdutton@gmail.com>
---
doc: define timestamp in pack protocol grammar
Fixes https://git.issues.gerritcodereview.com/issues/40000018
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2154%2Fheathdutton%2Fhd%2Fdoc-protocol-timestamp-40000018-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2154/heathdutton/hd/doc-protocol-timestamp-40000018-v1
Pull-Request: https://github.com/git/git/pull/2154
Documentation/gitprotocol-pack.adoc | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/gitprotocol-pack.adoc b/Documentation/gitprotocol-pack.adoc
index 837b691c89..7ad63322c2 100644
--- a/Documentation/gitprotocol-pack.adoc
+++ b/Documentation/gitprotocol-pack.adoc
@@ -273,6 +273,7 @@ out of what the server said it could do with the first 'want' line.
additional-want = PKT-LINE("want" SP obj-id)
depth = 1*DIGIT
+ timestamp = 1*DIGIT
filter-request = PKT-LINE("filter" SP filter-spec)
----
base-commit: 68cb7f9e92a5d8e9824f5b52ac3d0a9d8f653dbe
--
gitgitgadget
next reply other threads:[~2026-01-04 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 3:08 Heath Dutton🕴️ via GitGitGadget [this message]
2026-01-04 6:28 ` [PATCH] doc: define timestamp in pack protocol grammar Junio C Hamano
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.2154.git.git.1767496120852.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=heathdutton@gmail.com \
--cc=jrnieder@gmail.com \
/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.