git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Nov 2021, #02; Wed, 3)

From
Han-Wen Nienhuys <hanwen@google.com>
Date
Nov 8, 2021, 10:33 UTC
Message-ID
<CAFQ2z_P8QGvSs5zwyOcBsbBiq+-rXSJpXzgOwwi_eg1ZB6cSSA@mail.gmail.com>
In-Reply-To
<xmqq8ry44vve.fsf@gitster.g>
On Thu, Nov 4, 2021 at 1:17 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 5 quoted lines
>
> 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.

Is there something stopping this topic from graduating to next, and if so what?
-- 
Han-Wen Nienhuys - Google Munich
I work 80%. Don't expect answers from me on Fridays.
--
Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Previous: Emily ShafferNext: Junio C Hamano
Message 3 of 4 in “What's cooking in git.git (Nov 2021, #02; Wed, 3)”
  1. Junio C HamanoNov 4, 2021
  2. submodules ux overhaul update (was: What's cooking in git.git (Nov 2021, #02; Wed, 3))Emily Shaffer, Nov 4, 2021
  3. Han-Wen NienhuysNov 8, 2021
  4. Junio C HamanoNov 8, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.