Feature Request: 'bzr mv --after' to tell bzr that file(s) have already been moved in the working tree

[John Arbash Meinel]

Hanns-Steffen Eichenberg wrote:
> An automatic detection of moved files would be great, but i think you
> have to have an explicit option in addition. Why? When refactoring Java
> Code (rename a class, for example), the name of the file AND the file
> content changes simultaneously. It is an atomic operation from within
> Eclipse (and all other major Java IDEs). How can this be later detected
> by an algorithm?
> 
> Ciao,
>   Steffen (scameronde)
> 

It wasn't auto-detection of the file move, just that when you type "bzr
mv x y" if x did not exist, but y did, it would just record the move,
rather than failing because x could not be moved.

The basic rule would be:
  source was versioned (it has an inventory record)
  source is not present on disk
  target is not versioned
  target is present on disk

That said, I think a big knob for '--after' is fine to add. Because it
also lets you do:

$ mv a b
$ touch a
*oops* forgot to record the move
$ bzr mv --after a b
$ bzr add a

As far as a name for it. '--after' is okay, and if it is consistent with
other VCSs, then that is a good reason to use it. There are other
possibilities (--record-only), but nothing that stands out as being good
enough to break compatibility with others.

I thought I saw you mention on IRC you actually wrote a patch for this,
which I would be happy to look over.

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20061103/36bd7972/attachment.pgp