Subject: Re: .git/info/refs

From: Jakub Narebski <[email-masked]>
Date: Wed, 24 Jan 2007 18:25:38 +0100

H. Peter Anvin wrote:

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