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

Re: What's cooking in git.git (Jul 2022, #02; Fri, 8)

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 10, 2022, 22:56 UTC
Message-ID
<xmqqk08kpoen.fsf@gitster.g>
In-Reply-To
<xmqq4jzquiok.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
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).  Commits prefixed with '-' are only in 'seen',
> and aren't considered "accepted" at all.

In this edition of the report, the topics that were kept on hold in the 'next' branch were by mistake left with the "Will cook in 'next'" label, but please consider them as "Will merge to 'master'" material.

Namely, the following 6 topics are already marked for 'master' in my updated copy of the "What's cooking" report and will be merged down accordingly.

Show 6 quoted lines
> * cr/setup-bug-typo (2022-06-17) 1 commit
> * jk/optim-promisor-object-enumeration (2022-06-16) 1 commit
> * rs/archive-with-internal-gzip (2022-06-15) 6 commits
> * ds/branch-checked-out (2022-06-21) 7 commits
> * jc/resolve-undo (2022-06-09) 1 commit
> * ac/bitmap-format-doc (2022-06-16) 3 commits
Thanks.
Previous: lilinchao@oschina.cn
Message 7 of 7 in “What's cooking in git.git (Jul 2022, #02; Fri, 8)”
  1. Junio C HamanoJul 9, 2022
  2. lilinchao@oschina.cnJul 10, 2022
  3. Junio C HamanoJul 10, 2022
  4. lilinchao@oschina.cnJul 10, 2022
  5. Junio C HamanoJul 11, 2022
  6. lilinchao@oschina.cnJul 11, 2022
  7. Junio C HamanoJul 10, 2022

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.