Re: [PATCH v2 02/10] Documentation/glossary: clarify limitations of pseudorefs

From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Date: Apr 30, 2024, 13:35 UTC
Message-ID: <777fa7d3-17f8-4883-9f9a-c4077866d394@app.fastmail.com>
In-Reply-To: <1f2f8cf3f2cfba65787551ce6571376275ef3a8d.1714479928.git.ps@pks.im>

On Tue, Apr 30, 2024, at 14:26, Patrick Steinhardt wrote:

>   - They are not surfaced when iterating through refs, like when using
>     git-for-each-ref(1). They are no ref, so iterating through refs
>     should not surface them.

s/They are no ref/They are not refs

-- 
Kristoffer Haugsbakk

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