git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2019, #03; Wed, 13)
Date: Wed, 13 Feb 2019 21:49:13 -0800
Message-ID: <xmqqzhqy9axy.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190214035944.GB7209@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

> On Wed, Feb 13, 2019 at 07:33:22PM -0800, Junio C Hamano wrote:
>
>> [Graduated to "master"]
>> [...]
>> * js/smart-http-detect-remote-error (2019-02-06) 3 commits
>>   (merged to 'next' on 2019-02-06 at ec1a6f67c1)
>>  + t5551: test server-side ERR packet
>>  + 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.
>
> Hmm, this was maybe a risky one to merge as part of -rc1. It is just
> enforcing the rules from the spec document, but it's possible that it
> may trigger on some poorly-behaved server.
>
> I'm not worried enough to suggest pulling it back, but it's something we
> should keep an eye on during the -rc period.

True.  I actually think that it is probably a good idea to unleash
this kind of thing as quickly as possible to the real world.  Those
outside the project, or even inside it, tend to only discover issues
after a feature release is made, so while I am generally in favor of
merging a new and potentially disruptive change in an early batch
after a feature release to 'master' (which would give us enough time
to fix things up until the next release), I do not think that
approach would help third-party interop issues very much.

.

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14  3:33 Junio C Hamano
2019-02-14  3:59 ` Jeff King
2019-02-14  5:49   ` Junio C Hamano [this message]
2019-02-14  5:53     ` Jeff King
2019-02-14  6:49       ` Todd Zullinger
2019-02-14  6:54         ` Jeff King
2019-02-14 20:10 ` Jonathan Tan
2019-02-14 20:47   ` Junio C Hamano

Reply instructions:

You may reply publically 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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqzhqy9axy.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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

git@vger.kernel.org list mirror (unofficial, one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.org/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox