Re: [PATCH 0/4] for-each-ref: introduce seeking functionality via '--skip-until'

From: Phillip Wood <phillip.wood123@gmail.com>
Date: Jul 2, 2025, 14:14 UTC
Message-ID: <5e9b3ef1-931b-4b70-8275-5aed5da3d6f3@gmail.com>
In-Reply-To: <20250701-306-git-for-each-ref-pagination-v1-0-4f0ae7c0688f@gmail.com>

Hi Karthik

On 01/07/2025 16:03, Karthik Nayak wrote:

Show 5 quoted lines

> 
> This enables efficient pagination workflows like:
>      git for-each-ref --count=100
>      git for-each-ref --count=100 --skip-until=refs/heads/branch-100
>      git for-each-ref --count=100 --skip-until=refs/heads/branch-200

Doesn't that require you to know the name of the ref after the last one returned by the previous batch? If the use case here is pagination then being able to provide a numeric offset might be a better fit. For example

	git for-each-ref --count=100 --start=200

would show refs 200 to 300

Thanks

Phillip

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