From: Josh Steadmon <steadmon@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2018, #01; Sun, 9)
Date: Mon, 10 Dec 2018 10:53:21 -0800 [thread overview]
Message-ID: <20181210185321.GB37614@google.com> (raw)
In-Reply-To: <xmqq8t0z3xcc.fsf@gitster-ct.c.googlers.com>
On 2018.12.09 17:42, Junio C Hamano wrote:
> * js/protocol-advertise-multi (2018-11-17) 1 commit
> - protocol: advertise multiple supported versions
>
> The transport layer has been updated so that the protocol version
> used can be negotiated between the parties, by the initiator
> listing the protocol versions it is willing to talk, and the other
> side choosing from one of them.
>
> How's the doneness of this one?
I'm not sure if you're asking me specifically or the list in general,
but I haven't heard any complaints about this, and there are no
outstanding requests on the review thread.
> * js/smart-http-detect-remote-error (2018-11-17) 3 commits
> (merged to 'next' on 2018-11-18 at 5c6edfcb85)
> + remote-curl: die on server-side errors
> + remote-curl: tighten "version 2" check for smart-http
> + remote-curl: refactor smart-http discovery
>
> Some errors from the other side coming over smart HTTP transport
> were not noticed, which has been corrected.
>
> Will cook in 'next'.
Masaya had a series that addresses this as well:
https://public-inbox.org/git/20181127045301.103807-1-masayasuzuki@google.com/
To combine these, we'd want to drop the diff to remote-curl.c in the
final patch of this series.
next prev parent reply other threads:[~2018-12-10 18:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 8:42 What's cooking in git.git (Dec 2018, #01; Sun, 9) Junio C Hamano
2018-12-09 9:03 ` Denton Liu
2018-12-10 3:21 ` Junio C Hamano
2018-12-10 3:52 ` Denton Liu
2018-12-10 10:26 ` Junio C Hamano
2018-12-09 20:31 ` pw/add-p-select, was " Johannes Schindelin
2018-12-10 10:42 ` Phillip Wood
2018-12-11 9:56 ` Johannes Schindelin
2018-12-11 14:48 ` Phillip Wood
2019-01-21 20:58 ` Johannes Schindelin
2019-01-22 20:27 ` Phillip Wood
2018-12-10 18:53 ` Josh Steadmon [this message]
2018-12-11 1:43 ` Junio C Hamano
2018-12-10 20:05 ` Elijah Newren
2018-12-10 21:50 ` Ævar Arnfjörð Bjarmason
2018-12-11 1:49 ` Junio C Hamano
2018-12-11 1:48 ` Junio C Hamano
2018-12-11 2:00 ` Stefan Beller
2018-12-11 6:17 ` Junio C Hamano
2018-12-16 21:48 ` Alban Gruin
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=20181210185321.GB37614@google.com \
--to=steadmon@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.