{"thread":{"id":"55159","subject":"[OUTREACHY][PATCH v1] doc: fix naming of response-end-pkt","startedAt":"2021-02-16T21:22:37Z","lastAt":"2021-02-18T00:01:20Z","messageCount":4,"participants":["Joey Salazar","Junio C Hamano","Denton Liu"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"417108","messageId":"5qGT6uzPLUGN2DXCMTzhixEhKHwaT6hODaOHQ485sfCROycrTDPx6P2Nd5dOy4J-gnhb_lKpxW4jJqhut-4gmoeIyuhpqbA5fXCeHoKHrK8=@protonmail.com","threadId":"55159","inReplyTo":null,"subject":"[OUTREACHY][PATCH v1] doc: fix naming of response-end-pkt","fromName":"Joey Salazar","fromEmail":"jgsal@protonmail.com","sentAt":"2021-02-16T21:21:50Z","receivedAt":"2021-02-16T21:22:37Z","isPatch":true,"sender":{"key":"jgsal@protonmail.com","avatar":null},"body":"Git Protocol version 2[1] defines 0002 as a Message Packet that indicates\nthe end of a response for stateless connections.\n\nChange the naming of the 0002 Packet to 'Response end' to match the\nparsing introduced in Wireshark's MR !1922 for consistency.\n\n[1] kernel.org/pub/software/scm/git/docs/technical/protocol-v2.html\n[2] gitlab.com/wireshark/wireshark/-/merge_requests/1922\n\nSigned-off-by: Joey Salazar \n---\n Documentation/technical/protocol-v2.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/technical/protocol-v2.txt b/Documentation/technical/protocol-v2.txt\nindex e597b74da39..6c55d566d8b 100644\n--- a/Documentation/technical/protocol-v2.txt\n+++ b/Documentation/technical/protocol-v2.txt\n@@ -33,8 +33,8 @@ In protocol v2 these special packets will have the following semantics:\n\n * '0000' Flush Packet (flush-pkt) - indicates the end of a message\n * '0001' Delimiter Packet (delim-pkt) - separates sections of a message\n- * '0002' Message Packet (response-end-pkt) - indicates the end of a response\n- for stateless connections\n+ * '0002' Response end Packet (response_end-pkt) - indicates the end of a\n+ response for stateless connections\n\n Initial Client Request\n ----------------------\n--\n2.29.0.rc2\n\n"},{"id":"417120","messageId":"xmqqlfbnobsd.fsf@gitster.c.googlers.com","threadId":"55159","inReplyTo":"5qGT6uzPLUGN2DXCMTzhixEhKHwaT6hODaOHQ485sfCROycrTDPx6P2Nd5dOy4J-gnhb_lKpxW4jJqhut-4gmoeIyuhpqbA5fXCeHoKHrK8=@protonmail.com","subject":"Re: [OUTREACHY][PATCH v1] doc: fix naming of response-end-pkt","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2021-02-16T23:03:46Z","receivedAt":"2021-02-16T23:04:50Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Joey Salazar writes:\n\n> Git Protocol version 2[1] defines 0002 as a Message Packet that indicates\n> the end of a response for stateless connections.\n>\n> Change the naming of the 0002 Packet to 'Response end' to match the\n> parsing introduced in Wireshark's MR !1922 for consistency.\n>\n> [1] kernel.org/pub/software/scm/git/docs/technical/protocol-v2.html\n> [2] gitlab.com/wireshark/wireshark/-/merge_requests/1922\n>\n> Signed-off-by: Joey Salazar \n> ---\n> Documentation/technical/protocol-v2.txt | 4 ++--\n> 1 file changed, 2 insertions(+), 2 deletions(-)\n\nThis came from b0df0c16 (stateless-connect: send response end\npacket, 2020-05-19), didn't it?\n\nThe original commit even says \"response end packet\" on its title, so\nI am reasonably sure the patch under discussion is an improvement ;-)\n\nHaving said that, asking its author to review the change would be\nthe most appropriate (cc'ed).\n\nThanks.\n\n>\n> diff --git a/Documentation/technical/protocol-v2.txt b/Documentation/technical/protocol-v2.txt\n> index e597b74da39..6c55d566d8b 100644\n> --- a/Documentation/technical/protocol-v2.txt\n> +++ b/Documentation/technical/protocol-v2.txt\n> @@ -33,8 +33,8 @@ In protocol v2 these special packets will have the following semantics:\n>\n> * '0000' Flush Packet (flush-pkt) - indicates the end of a message\n> * '0001' Delimiter Packet (delim-pkt) - separates sections of a message\n> - * '0002' Message Packet (response-end-pkt) - indicates the end of a response\n> - for stateless connections\n> + * '0002' Response end Packet (response_end-pkt) - indicates the end of a\n> + response for stateless connections\n>\n> Initial Client Request\n> ----------------------\n> --\n> 2.29.0.rc2\n"},{"id":"417152","messageId":"YCz4+xPVyL+hTZzR@generichostname","threadId":"55159","inReplyTo":"5qGT6uzPLUGN2DXCMTzhixEhKHwaT6hODaOHQ485sfCROycrTDPx6P2Nd5dOy4J-gnhb_lKpxW4jJqhut-4gmoeIyuhpqbA5fXCeHoKHrK8=@protonmail.com","subject":"Re: [OUTREACHY][PATCH v1] doc: fix naming of response-end-pkt","fromName":"Denton Liu","fromEmail":"liu.denton@gmail.com","sentAt":"2021-02-17T11:07:39Z","receivedAt":"2021-02-17T11:08:42Z","isPatch":true,"sender":{"key":"liu.denton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9620836?v=4"},"body":"Hi Joey,\n\nOn Tue, Feb 16, 2021 at 09:21:50PM +0000, Joey Salazar wrote:\n> Git Protocol version 2[1] defines 0002 as a Message Packet that indicates\n> the end of a response for stateless connections.\n> \n> Change the naming of the 0002 Packet to 'Response end' to match the\n> parsing introduced in Wireshark's MR !1922 for consistency.\n\nThanks for catching this, this is an obvious error on my part. In fact,\nI'd go as far as saying that in the commit where this was defined,\nb0df0c16 (stateless-connect: send response end packet, 2020-05-19), I\nerroneously called it a \"Message Packet\" when I meant to type \"Response\nEnd Packet\", which you are now correcting.\n\n> [1] kernel.org/pub/software/scm/git/docs/technical/protocol-v2.html\n> [2] gitlab.com/wireshark/wireshark/-/merge_requests/1922\n> \n> Signed-off-by: Joey Salazar \n> ---\n> Documentation/technical/protocol-v2.txt | 4 ++--\n> 1 file changed, 2 insertions(+), 2 deletions(-)\n> \n> diff --git a/Documentation/technical/protocol-v2.txt b/Documentation/technical/protocol-v2.txt\n> index e597b74da39..6c55d566d8b 100644\n> --- a/Documentation/technical/protocol-v2.txt\n> +++ b/Documentation/technical/protocol-v2.txt\n> @@ -33,8 +33,8 @@ In protocol v2 these special packets will have the following semantics:\n> \n> * '0000' Flush Packet (flush-pkt) - indicates the end of a message\n> * '0001' Delimiter Packet (delim-pkt) - separates sections of a message\n> - * '0002' Message Packet (response-end-pkt) - indicates the end of a response\n> - for stateless connections\n> + * '0002' Response end Packet (response_end-pkt) - indicates the end of a\n> + response for stateless connections\n\nA couple of aesthetic details: I see that these changes are based on MR\n!1922 so if you decide to take these suggestions, you'll probably need\nto apply them there too.\n\n\t1. It'd probably read better as \"Response End Packet\" (with the\n\t \"e\" capitalised)\n\n\t2. The mix of underscore and hyphen in response_end-pkt is a\n\t little odd, although I see that you've done it to make it\n\t match the surrounding code[3].\n\nI think that I'd prefer if 1. is taken and 2. can be ignored. But with\nor without those changes, consider this patch\n\n\tAcked-by: Denton Liu \n\nThanks,\nDenton\n\n[3]: https://gitlab.com/wireshark/wireshark/-/merge_requests/1922#note_502316230\n\n> Initial Client Request\n> ----------------------\n> --\n> 2.29.0.rc2\n> \n"},{"id":"417251","messageId":"mFXIveS58B7aSefQQEpY87ZyWBBrDhKPgOyEdriyZiD3Dn61_bhvLaJbjzGFRnX0rX7Zjvvxqobf684akMJYjd6qpFBVVMjwtKoFA2hSO_k=@protonmail.com","threadId":"55159","inReplyTo":"YCz4+xPVyL+hTZzR@generichostname","subject":"Re: [OUTREACHY][PATCH v1] doc: fix naming of response-end-pkt","fromName":"Joey Salazar","fromEmail":"jgsal@protonmail.com","sentAt":"2021-02-17T23:59:47Z","receivedAt":"2021-02-18T00:01:20Z","isPatch":true,"sender":{"key":"jgsal@protonmail.com","avatar":null},"body":"Hi Denton,\n\nOn Wednesday, February 17, 2021 5:07 AM, Denton Liu wrote:\n\n> Hi Joey,\n>\n> A couple of aesthetic details: I see that these changes are based on MR\n> !1922 so if you decide to take these suggestions, you'll probably need\n> to apply them there too.\n>\n> 1. It'd probably read better as \"Response End Packet\" (with the\n> \"e\" capitalised)\n>\n> 2. The mix of underscore and hyphen in response_end-pkt is a\n> little odd, although I see that you've done it to make it\n> match the surrounding code[3].\n\nWell noted, I'll follow up shortly with PATCH v2 to incorporate both changes.\n\nThank you,\nJoey\n"}]}