[BUG] git-rev-list: --topo-order --boundary and --max-count

From: Santi Béjar <sbejar@gmail.com>
Date: Mar 5, 2007, 10:02 UTC
Message-ID: <8aa486160703050202y5ee159d2i42a2859a00b41679@mail.gmail.com>

Hi *,

  the --topo-order does not play well with --boundary and --max-count.

$ git-rev-list --boundary --max-count=50 5ced0 | wc -l 56 $ git-rev-list --topo-order --boundary --max-count=50 5ced0 | wc -l 8846

(5ced0 is git.git's master). I think it should be 56 for both. It presents this behaviour since c4025103fa, when was added --boundary support for git-rev-list --max-count and --max-age.

Santi

$ 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.