Re: A shortcoming of the git repo format

From: H. Peter Anvin <hpa@zytor.com>
Date: Apr 27, 2005, 18:03 UTC
Message-ID: <426FD3EE.5000404@zytor.com>
In-Reply-To: <Pine.LNX.4.58.0504270820370.18901@ppc970.osdl.org>

Linus Torvalds wrote:

Show 16 quoted lines

> 
> On Tue, 26 Apr 2005, H. Peter Anvin wrote:
> 
>>One solution to all of this would be to define a quoting standard for 
>>strings, and simply require that all free-format strings (like the 
>>author fields) or at least strings that match [0-9a-f]{20}, are always 
>>quoted.
> 
> 
> git uses more of the ".newsrc" format, in that it just knows which 
> characters are legal or not.
> 
> To find the email address, look for the first '<'. To find the date, look 
> for the first '>'. Those characters are not allowed in the name or the 
> email, so they act as well-defined delimeters.
>

That's true for email addresses, but the point was to distinguish links to other git objects from any other kind of text. Currently there is no such delimiter for that. Another solution than the one I posted would be to define such a delimiter, for example '<' + 20 hex character + '>' (which would be distinguished from email addresses by the lack of an @ sign.) That would be a repo change, though.

Given no prior constraints, I would probably argue for a format which makes the data type known as a matter of syntax, using "..." quoted strings for *ALL* arbitrary strings, a different syntax for numbers and links, and leaving the door open for new data types like lists in the future.

	-hpa