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

[José Orlando Pereira]

On Friday 03 November 2006 2:02 pm, 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?

Although it probably shouldn't be default behavior, it would be nice to have a 
bzr plugin that used something like ESR's "comparator" [1] to detect 
similarity between (1) known files that are gone from the working dir and (2) 
unknown files present in the working dir and then suggest a set of likely bzr 
mv --after operations that the user can veto or accept.

A simple comparison of entire file hashes doesn't cut it, as Java refactoring 
makes (minor) changes to file content.

[1] http://catb.org/~esr/comparator/

-- 
Jose Orlando Pereira