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

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hanns-Steffen Eichenberg wrote:
> This patch is a draft.

> Here it is. Since this is my first work for bzr and my first lines of
> python for more than 3 years i would be happy if
> you can give the code a thorough review.

Thanks for working on this.  Please don't zip your patches in the
future-- just attach them.  Zipping them
 - makes it harder to discuss on the mailing list
 - prevents Bundle Buggy from showing the patch
 - prevents Bundle Buggy from auto-tracking whether a bundle is merged
   or superseded.

> What i have done:
>   - modified the move code and the command line documentation  
>   - some tests on the command line with a real world project
> 
> What i have not done:
>   - written any tests, because i do not know where and how. I would
> appreciate some help here

It's described in HACKING, under "Writing tests".  In this case, you'd
want to add additional tests to "bzrlib/blackbox/test_mv.py".  Did you
have other questions about writing tests?

>   - run 'bzr selftest', because the selftest of 'bzr.dev' seems to hang
> on my machine

That's pretty serious.  Does "bzr selftest whoami" hang, or is it only
long runs that hang?  Does a progress bar show?  Does it print anything?

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFFT0uj0F+nu1YWqI0RAq8JAKCE++nZErz8Wi6Hu7B4/EHEHSnPSACfbQTa
Bqw7FeRe48YD5eFpiTyho9I=
=frm9
-----END PGP SIGNATURE-----