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

From: Andreas Schwab <schwab@linux-m68k.org>
Date: Jul 4, 2025, 14:52 UTC
Message-ID: <87ikk8c8jr.fsf@igel.home>
In-Reply-To: <CAOLa=ZS0uP+5xso_SEG2GJZHeac-0F2_wMJKtvbFj_wROKbBkw@mail.gmail.com>

On Jul 04 2025, Karthik Nayak wrote:

Show 12 quoted lines

> Consider the example
>
>   $ git for-each-ref
>   refs/heads/bar
>   refs/heads/foo
>   refs/heads/main
>
>   $ git for-each-ref --seek=refs/heads/cat
>   refs/heads/foo
>   refs/heads/main
>
> You can see that the reference doesn't have to exist.

That is even more confusing. What is the first matching ref if none of them match? Doesn't that mean skipping _all_ refs?

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

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