[RFC] store inventory in tab-separated file
Aaron Bentley
aaron.bentley at utoronto.ca
Mon Feb 5 12:51:03 GMT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Pool wrote:
> On 2 Feb 2007, Alexander Belchenko <bialix at ukr.net> wrote:
>
>>> My pet desire for a new inventory format is I'd like each of the values
>>> to be annotated individually, so that we can do a completely
>>> annotate-based merge. (That works even with shallow branches that do
>>> not store their common base)
>> My initial attempt to create format of one entry like this:
>>
>> file bzrignore-20050311232317-81f7b71efa2db11a .bzrignore TREE_ROOT
>> revision xxxx
>> text_sha1 xxxx
>> text_size xxxx
>> executable yes
>>
>> If I understand you correctly you'd like to have this:
>>
>> file bzrignore-20050311232317-81f7b71efa2db11a
>> name .bzrignore
>> parent_id TREE_ROOT
>> revision xxxx
>> text_sha1 xxxx
>> text_size xxxx
>> executable yes
>>
>> Am I understand correctly this: "each of the values to be annotated individually"?
>>
>> This change complicate things a bit and probably slowdown read operation
>> because of additional checks but I try to test this implementation as well
>> to see real numbers.
>
> I'm not sure about Aaron, but I would think just having one line per
> file and seeing when it was last changed would be enough.
No, I actually meant each value, the way Alexander has it. That's what
you'd need to do an annotate merge correctly.
Though I do see how it breaks file_ids_altered_by_revision_ids, so it
may not be desirable.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFxyg30F+nu1YWqI0RAnqKAKCG8qtIddUdWo4jWCUB+uotr+SySgCdHxTn
wHpBO4LWthNbmEg5Db/PzRo=
=LA1k
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list