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

ds/revision-maximal-only (was Re: What's cooking in git.git (Jan 2026, #09))

From
Derrick Stolee <stolee@gmail.com>
Date
Jan 28, 2026, 14:29 UTC
Message-ID
<283c6bc4-787d-4035-bc94-a85ca775e8f0@gmail.com>
In-Reply-To
<xmqqecnbeyvr.fsf@gitster.g>
On 1/27/26 12:42 PM, Junio C Hamano wrote:
Show 8 quoted lines
> * ds/revision-maximal-only (2026-01-22) 1 commit
>   - revision: add --maximal-only option
> 
>   "git rev-list" and friends learn "--maximal-only" to show only the
>   commits that are not reachable by other commits.
> 
>   Will merge to 'next'?
>   source: <pull.2032.v2.git.1769097958549.gitgitgadget@gmail.com>

I believe that the discussion has landed in a place where this version is good to merge. Any remaining discussions around using the 'git merge-base --independent' algorithm when appropriate or adding '--maximal-only' to other builtins can be delayed to a future extension, I think.

Thanks, -Stolee

Previous: Junio C HamanoNext: brian m. carlson
Message 4 of 8 in “What's cooking in git.git (Jan 2026, #09)”
  1. Junio C HamanoJan 27, 2026
  2. Taylor BlauJan 27, 2026
  3. Junio C HamanoFeb 6, 2026
  4. ds/revision-maximal-only (was Re: What's cooking in git.git (Jan 2026, #09))Derrick Stolee, Jan 28, 2026
  5. brian m. carlsonJan 28, 2026
  6. brian m. carlsonJan 29, 2026
  7. Eric SunshineJan 29, 2026
  8. brian m. carlsonJan 29, 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.