list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: Junio C Hamano <>
To: Jeff King <>
Subject: Re: What's cooking in git.git (Feb 2019, #03; Wed, 13)
Date: Wed, 13 Feb 2019 21:49:13 -0800
Message-ID: <> (raw)
In-Reply-To: <> (Jeff King's message of "Wed, 13 Feb 2019 22:59:44 -0500")

Jeff King <> 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	other threads:[~2019-02-14  5:49 UTC|newest]

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 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:

  List information:

* 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 list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for the project(s) associated with this inbox:

AGPL code for this site: git clone