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

[Martin Geisler]

"Stephen J. Turnbull" <stephen at xemacs.org> writes:

> Martin Geisler writes:
>
>  > Note that Mercurial handles this case *exactly the same*.
>
> I don't understand what you mean.  Mercurial can't clone a branch with
> an empty directory in it accurately, and probably not a directory
> which contains only unregistered files (thanks for the eg, Liam).  So
> it can't even get started on this workflow.  A second workspace will
> have no "foo" directory to rename.

Ah, I misunderstood where you put the emphasis in the Bazaar example. I
focussed on merging foo/baz into bar/baz and you focussed on adding the
empty directory.

Mercurial can't handle empty directories, no quesiton about that.

> As I've said before, I don't care ("touch foo/.precious; hg add
> foo/.precious" Works For Me[tm]), but for some people (Brian Alwis's
> post) it's a use case they've encountered in practice. ("Java
> refactoring" seems to be a common keyword.)

No, refactoring with empty directories wont work in Mercurial.

-- 
Martin Geisler

Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20111025/e6efa854/attachment.pgp>