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

Re: What's cooking in git.git (May 2026, #04)

From
Mirko Faina <mroik@delayed.space>
Date
May 18, 2026, 15:54 UTC
Message-ID
<ags1rtQnlO6KB1-Q@exploit>
In-Reply-To
<xmqqv7clbizy.fsf@gitster.g>
On Mon, May 18, 2026 at 10:32:01AM +0900, Junio C Hamano wrote:
Show 8 quoted lines
> * mf/revision-max-count-oldest (2026-05-15) 1 commit
>  - revision.c: implement --max-count-oldest
> 
>  "git rev-list" (and "git log" family of commands) learned a new "--max-count-oldest"
>  that picks oldest N commits in the range instead of the usual newest.
> 
>  Will merge to 'next'?
>  source: <463cc8e2764edb7de3d379f615f5cfbd0919bfa3.1778887662.git.mroik@delayed.space>

Sorry, I realized it's still a bit buggy when coupled with --boundary. There will be a v8.

Previous: Junio C HamanoNext: Taylor Blau
Message 2 of 7 in “What's cooking in git.git (May 2026, #04)”
  1. Junio C HamanoMay 18, 2026
  2. Mirko FainaMay 18, 2026
  3. Taylor BlauMay 19, 2026
  4. Jeff KingMay 19, 2026
  5. Junio C HamanoMay 20, 2026
  6. Justin ToblerMay 19, 2026
  7. Junio C HamanoMay 20, 2026

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.