nested trees design-approach : composite trees vs iter_changes

[Robert Collins]

On Tue, 2009-05-05 at 10:40 +1000, Ian Clatworthy wrote:

> Thanks for articulating your concerns.
> 
> As best I can tell, your concerns are largely internal, implementation
> issues that don't impact end users. Can you give a concrete example of
> when the user experience will be unacceptable if the proposed code lands?

We have two sets of users:
 - those that write to the API, including casual scripters
 - those that don't.

I think users that don't write to the API at all will only see 'nested
tree support coming along'. It may not make much or any difference to
them.

I think users (which includes us) that write to the API will see most of
the things I enumerated bite them repeatedly. Its worth noting that such
users include sysadmins doing precommit hooks, integration into
buildbots and other such tasks.

Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090505/c0dfe5c2/attachment.pgp