Getting rid of RootEntry?

[Martin Pool]

On 17 Jan 2006, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:

> Martin Pool wrote:
> | On 16 Jan 2006, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
> 
> | Right, for example it would be a clean way to get nice user behaviour
> | when a file is replaced by a symlink of the same name.  Not allowing
> | files to change type seems to imply that at least internally there will
> | be an add & remove operation.  But as you say it does introduce more
> | edge cases and so room for bugs.
> 
> A simple approach would be to prefix the inventory ids with their
> filetype.

Well, in a sense this is internally an add and remove because the old
(composite) id is gone and a new one has appeared.  It might be a good
way to graft it in but perhaps it's simpler just to allow changes.

> But then diff and status would show adds/deletes instead of
> type changes.

Well, I suppose you could make them know about this and show it as a
kind change, but it's a bit kludgy.

> This may be one of those cases where we eventually have to put in hard
> labor to make things slightly easier for user.  But I'm happy to put it off.

Maybe it'd be easier to get systematically into the merge code after
your tree transform refactoring?  That would be the area I'd be most
concerned about affecting.

-- 
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060118/a169b804/attachment.pgp