From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Elijah Newren <newren@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2018, #01; Sun, 9)
Date: Mon, 10 Dec 2018 22:50:23 +0100 [thread overview]
Message-ID: <875zw1aw68.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <CABPp-BGVHnaZLg4fuptVmNa=jRHg0cMDTWjv1NdLQJXPe=+ahw@mail.gmail.com>
On Mon, Dec 10 2018, Elijah Newren wrote:
> On Sun, Dec 9, 2018 at 12:42 AM Junio C Hamano <gitster@pobox.com> wrote:
>
>> Git 2.20 has been tagged. I'd expect that we would slow down to see
>> how stable it is and queue only the brown-paper-bag fixes for a week
>> or so, before opening the tree for the next cycle, rewinding the tip
>> of 'next', etc.
>
> Does this mean you'd prefer we continue to wait a little longer before
> sending in new series and re-rolls, or just that you are managing
> expectations about when they might be queued?
>
> (Just curious whether I should submit my rebase-merge-on-sequencer
> re-roll or continue waiting. I'm happy to do whatever is more
> convenient for others.)
Related; Junio: I've submitted a few things in the last 2-3 weeks which
I knew weren't making it into 2.20, but I just wanted to kick out the
door as I had them ready. Things which are not noted in this "What's
Cooking".
I'm fine with re-submitting those once 2.21 picks up, but don't want to
needlessly spam if your plan is to circle around and pick up those
things you were (rightly) ignoring during the RC period.
next prev parent reply other threads:[~2018-12-10 21:50 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
2018-12-11 1:43 ` Junio C Hamano
2018-12-10 20:05 ` Elijah Newren
2018-12-10 21:50 ` Ævar Arnfjörð Bjarmason [this message]
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=875zw1aw68.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.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 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 NNTP newsgroup(s).