the inventory must be updated as merge proceeds, not at the end

[John Arbash Meinel]

Robert Collins wrote:
> On Tue, 2006-01-03 at 09:06 -0600, John Arbash Meinel wrote:
> 
> 
>>One of the formats could be '--format=tab', which would give you
>>something like the above.
>>I went with rio and python for starters, since python is useful for me
>>and bzr, and rio our current 'generic' format, which can handle spaces, etc.
>>csv or tab delimited might make sense as well.
>>
>>Also, do you have a thought as to what the 'date' field should be? Right
>>now I'm just using the current timestamp. But I'm thinking it probably
>>should be the time of the last commit, unless the tree is out of date.
>>(Which is only detected if you pass the --check-for-clean flag.)
>>
>>And for the 'file_versions', are you thinking to use revnos or revision
>>ids. A merge might introduce a last modified which is not in
>>revision-history.
>>
>>And what about dates for revisions? I just want the file to be useful,
>>without being too verbose.
> 
> 
> I wouldn't worry about size - clarity first in this case I think.
> 
> Rob
> 

Well, version-info for bzr.dev is 256k at this point. But it works.

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060103/b827a1e2/attachment.pgp