Re: .git/info/refs

From: Jakub Narebski <jnareb@gmail.com>
Date: Jan 24, 2007, 17:25 UTC
Message-ID: <ep83ur$p3i$2@sea.gmane.org>
In-Reply-To: <45B79208.2080502@zytor.com>

H. Peter Anvin wrote:

Show 7 quoted lines

>> I also expect that they interpret everything after the sha1 as refname, 
>> what with our having become quite liberal with refnames (they can contain 
>> spaces, tabs, and even a small amount of special K). So I don't see a way 
>> to upgrade the file format.
> 
> They can also contain newlines, probably, so escaping is obligatory
> anyway.

No, refnames can not contain newlines.

And .git/info/refs mimics git-ls-remote / git-peek-remote output, and is meant for dumb transports.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

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