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

[Robert Collins]

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

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060104/f8edb251/attachment.pgp