archive mirror
 help / color / mirror / Atom feed
From: "" <>
To: "Junio C Hamano" <>
Cc: git <>
Subject: Re: Re: [PATCH 2/2] remote-curl.c: handle v1 when check_smart_http
Date: Thu, 25 Mar 2021 12:22:45 +0800	[thread overview]
Message-ID: <> (raw)

>Junio C Hamano <> writes:
>>> +	} else if (!strcmp(reader.line, "version 1")) {
>>> +	die(_("v1 is just the original protocol with a version string, use v0 or v2 instead."));
>> The user may no longer get "invalid response; got 'version 1'", but
>> the above does not still explain why v1 is bad and v0 or v2 is
>> welcome, either.  IOW, I do not think the patch improves the message
>> to achieve what it attempted to do, i.e.
>>     ... but the other side just treat it as "invalid response", this
>>     can't explain why is not ok.
>	v1 is not supported; use v0 or v2
>would explain why the connection is refused.  It explains why it is
>not ok much clearly than "just the original with a version string".
>> I wonder if it is a sensible and better alternative to treat v1
>> response as if we got v0 (if v1 is truly the same as v0 except for
>> the initial version advertisement).
>> Input from those who are familiar with the protocol versions is very
>> much appreciated.
>This still stands; we reject because we don't support, but is it
>easy to support it instead, if there is no difference? 

Yes, if there is no difference, just to support it too. So I don't know
why it is not support until now.


  parent reply	other threads:[~2021-03-25  4:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-03-24  5:36 ` [PATCH 2/2] remote-curl.c: handle v1 when check_smart_http lilinchao
2021-03-24 20:28   ` Junio C Hamano
2021-03-24 20:33     ` Junio C Hamano
     [not found]     ` <>
2021-03-25  4:22       ` lilinchao [this message]
2021-03-26  6:24     ` Jeff King
2021-03-26  6:55       ` Jeff King
     [not found]     ` <>
2021-03-29  9:30       ` lilinchao
2021-03-29 10:40         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).