Proper tracking of file-level operations: rename, directories, merges

[Ben Finney]

Martin Geisler <mg at lazybytes.net> writes:

> Ben Finney <ben+bazaar at benfinney.id.au> writes:
>
> > I don't know why you're restricting the scope to merge; this is a
> > problem even if it doesn't affect merge.
>
> Okay, I'm restricting the scope to merge and log: this is where you want
> the rename information to be used -- this is where it *matters*.

I disagree with that restriction of scope. It matters in any interaction
with the tool. That's what I'm calling the tool's behaviour.

> > Mercurial fails to support the distinct operation that is requested
> > with ‘hg mv foo bar’, Bazaar supports it correctly, that's why I'm
> > saying Bazaar's behaviour is superior here and Mercurial's is buggy.
>
> But it does support it -- the output may just look funny to you.

If the output doesn't support it *as a rename*, then it's a bug in
behaviour from this user's POV.

From the user's POV, a rename is *not* a copy+delete. The tool can
represent it internally however you like, but if the tool's behaviour
doesn't consistently show the user what they asked to happen, then
that's a behaviour bug, IMO.

-- 
 \         “I got up the other day, and everything in my apartment has |
  `\   been stolen and replaced with an exact replica.” —Steven Wright |
_o__)                                                                  |
Ben Finney
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20111026/e3ee4159/attachment.pgp>