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

[Marius Kruger]

hi,
On 11/5/06, Hanns-Steffen Eichenberg <scameronde at googlemail.com> wrote:
>
> My current patch (draft version, not made public yet) uses a flag or the
> following logic:
>
>   - source present and versioned, target not present and not versioned:
> mv file and change repo (regular mv)
>   - source not present and versioned, target present and not versioned:
> only change repo (new mv)
>   - source present and versioned, target present and not versioned: you
> have to use the flag or it is an error
>         (for situations like:
>                    mv a b; touch a; bzr mv a b  ==> ERROR
>                    mv a b; touch a; bzr mv a b --after  ==> OK
>          )
>

This is perfect!
 (when can we have it :)

...
>
I think when using the fuzzy match the user must be the one who finally
> decides
> if a match is correct or not. Maybe the auto-rename could open an editor
> with
> its suggestions. That would allow for easy control and confirmation of
> mass
> renames.
>

This will be a very nice to have later.

Later mv-detection could also be done, when you run 'bzr status': also show
the proposed moves.
Then the user could alter this if needed with additional bzr command options
   - 'bzr mv --after a b'
   - 'bzr mv --cancel a b' (if the wrong one was chosen)
     (as the inverse of 'bzr add' is 'bzr remove', the user should be able
to cancel the mv action, in the case he made a mistake.)

regards
marius

-- 
--

The Source is strong with this one.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20061106/b5054e48/attachment.htm