From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
Brandon Williams <bmwill@google.com>,
Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: [PATCH] protocol: treat unrecognized protocol.version setting as 0
Date: Wed, 28 Feb 2018 10:06:19 -0800 [thread overview]
Message-ID: <xmqqtvu1kmzo.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqq7eqxm22w.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Wed, 28 Feb 2018 09:55:03 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>
>>> I wonder if it's better to specify multiple versions. If v2 is not
>>> recognized by this git but v0 is, then it can pick that up. But if you
>>> explicitly tell it to choose between v2 and v3 only and it does not
>>> understand either, then it dies. Not sure if this is a good idea
>>> though.
>>
>> Interesting thought. Something roughly like this (on top of the patch
>> this is a reply to)?
>
> I am OK with that, i.e. allow the user to tell us what is acceptable
> and pick from them, as long as the blind "we do not know so let's
> fall back to v0" is removed.
Sorry, but "as long as" was a bit too strong. I am not convinced
that the "treat unrecognized one as if it were 0" is a good idea for
the reasons I gave in the my earlier response, but I am not yet
convinced that erroring out is the best solution, either.
So s/as long as/but it may be better if/, perhaps.
next prev parent reply other threads:[~2018-02-28 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 0:50 [PATCH] protocol: treat unrecognized protocol.version setting as 0 Jonathan Nieder
2018-02-28 1:02 ` Brandon Williams
2018-02-28 1:10 ` Duy Nguyen
2018-02-28 1:16 ` Brandon Williams
2018-02-28 1:22 ` Jonathan Nieder
2018-02-28 17:55 ` Junio C Hamano
2018-02-28 18:06 ` Junio C Hamano [this message]
2018-02-28 17:53 ` Junio C Hamano
2018-02-28 18:07 ` Jonathan Nieder
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=xmqqtvu1kmzo.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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).