git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2018, #04; Fri, 17)
Date: Sat, 18 Aug 2018 13:10:34 +0200	[thread overview]
Message-ID: <877ekoq6ad.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqva88aa0c.fsf@gitster-ct.c.googlers.com>


On Fri, Aug 17 2018, Junio C Hamano wrote:

> Usually, I refrain from merging larger topics in 'next' down to
> 'master' when we get close to -rc0, but I am wondering if it is
> better to merge all of them to 'master', even the ones on the larger
> and possibly undercooked side, expecting that we collectively spend
> effort on hunting and fixing bugs in them during the pre-release
> freeze period.  If we were to go that route, I'd want everybody's
> buy-in and I'll promise to ignore any shiny new toys that appear on
> list that are not regression fixes to topics merged to 'master'
> since the end of the previous cycle to make sure people are not
> distracted.

I'm very much up for this. We have some very useful things (like
range-diff and midx) sitting in "next". I think if you merge next down
to master now we'll have plenty of time to smoke out bugs & regressions
before 2.19.

  parent reply	other threads:[~2018-08-18 11:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 22:44 What's cooking in git.git (Aug 2018, #04; Fri, 17) Junio C Hamano
2018-08-18  6:29 ` Duy Nguyen
2018-08-18  6:59 ` Jonathan Nieder
2018-08-20 17:26   ` Junio C Hamano
2018-08-20 18:14     ` Derrick Stolee
2018-08-18  9:34 ` Christian Couder
2018-08-18 11:34   ` Ævar Arnfjörð Bjarmason
2018-08-18 12:54     ` Christian Couder
2018-08-18 11:10 ` Ævar Arnfjörð Bjarmason [this message]
2018-08-20 10:23 ` Phillip Wood
2018-08-20 17:44   ` Eric Sunshine
2018-08-20 19:36   ` pw/rebase-i-author-script-fix, was " Johannes Schindelin
2018-08-20 18:11 ` Stefan Beller
2018-08-20 21:32   ` Junio C Hamano
2018-08-20 18:19 ` 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

  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=877ekoq6ad.fsf@evledraar.gmail.com \
    --to=avarab@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).