From: Junio C Hamano <gitster@pobox.com>
To: Han-Wen Nienhuys <hanwen@google.com>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: What's cooking in git.git (Nov 2021, #02; Wed, 3)
Date: Mon, 08 Nov 2021 12:15:00 -0800 [thread overview]
Message-ID: <xmqqfss6tnej.fsf@gitster.g> (raw)
In-Reply-To: <CAFQ2z_P8QGvSs5zwyOcBsbBiq+-rXSJpXzgOwwi_eg1ZB6cSSA@mail.gmail.com> (Han-Wen Nienhuys's message of "Mon, 8 Nov 2021 11:33:25 +0100")
Han-Wen Nienhuys <hanwen@google.com> writes:
> On Thu, Nov 4, 2021 at 1:17 AM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> Here are the topics that have been cooking in my tree. Commits
>> prefixed with '+' are in 'next' (being in 'next' is a sign that a
>> topic is stable enough to be used and are candidate to be in a
>> future release).
> ..
>> * hn/reftable (2021-10-08) 19 commits
>> - Add "test-tool dump-reftable" command.
>>..
>
> As this topic has no interaction with any other code in Git, leaving
> it cooking in 'seen' for longer doesn't provide any extra test
> assurances.
Yeah, as long as it does not break how well the existing file-based
ref backend works, it would be OK, because even if we later find a
big bug in the reftable code, nobody would get hurt by the code we
currently have in 'seen'.
> Is there something stopping this topic from graduating to next, and if so what?
Post release rebuilding of 'next', I would say, at this late point
in the cycle. If those who are tired of waiting can start reviewing
each other's topics and work on improving them in the meantime, it
would help us to use our time better during the next cycle, I would
guess.
Thanks.
prev parent reply other threads:[~2021-11-08 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 0:17 What's cooking in git.git (Nov 2021, #02; Wed, 3) Junio C Hamano
2021-11-04 21:21 ` submodules ux overhaul update (was: What's cooking in git.git (Nov 2021, #02; Wed, 3)) Emily Shaffer
2021-11-08 10:33 ` What's cooking in git.git (Nov 2021, #02; Wed, 3) Han-Wen Nienhuys
2021-11-08 20:15 ` Junio C Hamano [this message]
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=xmqqfss6tnej.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@google.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).