[BUG] spurious tree root changes in workingtree2 and 3

Robert Collins robertc at robertcollins.net
Thu Aug 23 21:48:05 BST 2007

On Thu, 2007-08-23 at 16:25 -0400, Aaron Bentley wrote:
> Hash: SHA1
> Robert Collins wrote:
> > On Thu, 2007-08-23 at 08:52 -0400, Aaron Bentley wrote:
> >> Formats that don't support unique roots also don't treat the tree root
> >> as a proper directory.  knit1 doesn't store a knit for it.  Its
> >> inventory format doesn't record roots as proper directories, so they
> >> lack a revision attribute. 
> > 
> > Ah, so where does the .revision value come from in the inventory then?
> Repository.deserialise_inventory:

>         result.root.revision = revision_id


I realise this has probably been done to death somewhat; but what do you
think of exposing 'None' as the revision in this case? It would let me
detect when it should not be included in the commit candidates list.

As far as the changes to recorded transitive alterations in inventories,
its not clear to me that that will affect the last_modified flag. It may
well just add another field, or be an emergent aspect of the storage.

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/20070824/afced365/attachment-0001.pgp 

More information about the bazaar mailing list