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

On Wed, Feb 13, 2019 at 09:49:13PM -0800, Junio C Hamano wrote:

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

Yeah, I do have the feeling that not many people really exercise our -rc
candidates. I'm not sure how to improve that. We could try to push
packagers to make them available (and I think Jonathan already does for
Debian's "experimental" track). But ultimately I think it is not a
packaging/availability question, but just that most people do not bother
until there is a real release.

-Peff

  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
2019-02-14  5:53     ` Jeff King [this message]
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=20190214055315.GK20578@sigill.intra.peff.net \
    --to=peff@peff.net \
    --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

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