Re: with git update-ref?

From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Oct 11, 2024, 20:56 UTC
Message-ID: <cb60b7ad-7902-4293-81e9-06d1b1526842@app.fastmail.com>
In-Reply-To: <D4T9VCF8OS6U.1FMB8P6YU7I3S@ferdinandy.com>

On Fri, Oct 11, 2024, at 22:51, Bence Ferdinandy wrote:

Show 11 quoted lines

> Hi,
>
> the documentation for `git update-ref` has this sentence:
>
>> It also allows a "ref" file to be a symbolic pointer to another
>> ref file by starting with the four-byte header sequence of
>> "ref:".
>
> After fumbling around a bit and getting errors like 
>
> fatal: ref:refs/remotes/origin/test: not a valid SHA1

`ref: refs/remotes/origin/test`? (space after colon)

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