nested tree remaining questions

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Collins wrote:
| Open discussion points AFAIK:
|  * what id should the node for the nested tree have in the parent. I
| think it should be the root id of the child tree. Seeking +1 or
| discussion on this.

+1

|  * what data should be 'in' the node? At UBZ we discussed just the revid
| of the revision present when we committed. I think that this is fine and
| suitable - we proposed a hinting mechanism for finding that revision and
| that root id to reproduce the tree called '.bzr-child-locations'.
| Seeking a +1 on the 'content is the revision id of the child' to
| finalise this.

+1 on content is the revision id of the child

|  * What should .bzr-child-locations look like. At UBZ it was a control
| file in the source tree. I think now that its better to have it as bzr
| managed data - add a 'bzr edit-child-locations' command to show it to
| the user, but not pollute their tree with [and incidentally allow us to
| extend the format in the future]. Seeking a +1 on '.bzr-child-locations
| is versioned data'

+1 from mr. "let's not do any more versioned control files", himself.

|  * What child location data do we need? I think all we need is
| rootid:url pairs. We can of course try all the urls, but the root id is
| a nice hint. multiple entries per url and per rootid are allowed, to
| give fallback facilities and the like. Seeking a +1 on this.

I'm not really clear on what this is for.  Wouldn't it make more sense
to associate the data with the nested trees themselves?  And if the
nested tree has a branch, should it be updated?

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD6VrW0F+nu1YWqI0RAsH3AJ9+5r4J3VB1f7wdRtyrQzA8aguawQCeMVum
ehN48+K5Jx2+vU0O0jiAWEs=
=cWfk
-----END PGP SIGNATURE-----