From: Junio C Hamano <gitster@pobox.com>
To: Calvin Wan <calvinwan@google.com>
Cc: git@vger.kernel.org, Ivan Frade <ifrade@google.com>
Subject: Re: [PATCH v2] protocol-v2.txt: align delim-pkt spec with usage
Date: Thu, 11 Nov 2021 14:53:02 -0800 [thread overview]
Message-ID: <xmqqpmr6jodt.fsf@gitster.g> (raw)
In-Reply-To: <20211111220048.1702896-1-calvinwan@google.com> (Calvin Wan's message of "Thu, 11 Nov 2021 22:00:48 +0000")
Calvin Wan <calvinwan@google.com> writes:
> The current protocol EBNF allows command-request to end with the
> capability list, if no command specific arguments follow, but the
> protocol requires that after the capability list, there must be a
> delim-pkt regardless of the number of command specific arguments. Fixed
> the EBNF to match. Both JGit and libgit2's implementation has the
> delim-pkt as mandatory. JGit's code is not publicly linkable, but
> libgit2 is linked below[1]. As for currently implemented commands on v2
> (ls-ref and fetch), the delim packet is already being passed through
>
> [1]: https://github.com/libgit2/libgit2/blob/main/src/transports/git.c
Thanks for an extra level of research. Very much appreciated.
Will queue.
>
> Reported-by: Ivan Frade <ifrade@google.com>
> Signed-off-by: Calvin Wan <calvinwan@google.com>
> ---
> Documentation/technical/protocol-v2.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/technical/protocol-v2.txt b/Documentation/technical/protocol-v2.txt
> index 21e8258ccf..8a877d27e2 100644
> --- a/Documentation/technical/protocol-v2.txt
> +++ b/Documentation/technical/protocol-v2.txt
> @@ -125,11 +125,11 @@ command can be requested at a time.
> empty-request = flush-pkt
> command-request = command
> capability-list
> - [command-args]
> + delim-pkt
> + command-args
> flush-pkt
> command = PKT-LINE("command=" key LF)
> - command-args = delim-pkt
> - *command-specific-arg
> + command-args = *command-specific-arg
>
> command-specific-args are packet line framed arguments defined by
> each individual command.
>
> base-commit: e9e5ba39a78c8f5057262d49e261b42a8660d5b9
prev parent reply other threads:[~2021-11-11 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 19:35 [RFC PATCH 0/1] protocol-v2.txt: align delim-pkt spec with usage Calvin Wan
2021-10-27 19:35 ` [RFC PATCH 1/1] " Calvin Wan
2021-10-27 21:44 ` Junio C Hamano
2021-11-11 22:00 ` [PATCH v2] " Calvin Wan
2021-11-11 22:09 ` Nasser Grainawi
2021-11-11 22:53 ` Junio C Hamano [this message]
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=xmqqpmr6jodt.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=calvinwan@google.com \
--cc=git@vger.kernel.org \
--cc=ifrade@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).