Q: Should 'bzr remove' take as long as 'bzr commit'

[John Arbash Meinel]

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


...
> 
> Oh, I realized the problem may be that we're checking whether the
> files are modified or not before deleting them, and that may take some
> time -- though I would still be surprised if it's 5 minutes, unless
> the disk is unusually slow.  It may be faster with --no-backup.

Well, if commit took 5min to process them, then it is reasonable to
assume 'rm' might take that long to process them. It wants to see if the
files have been modified since their commit, so that it can decide
whether to save them as a backup, or just nuke them.

It certainly does seem slow, but usually commit is slow because of the
number of files, and not because of the size of them.

> 
> If you can reproduce this, please send us instructions on how to do
> so, or file a bug.
> 
> Martin
> 


John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3Myf0ACgkQJdeBCYSNAAN77gCcD/qKrBm2JHx8vyuzuvOZclk1
POEAnR43T9yZL+UiOChUeYfqmt01ftip
=DLAT
-----END PGP SIGNATURE-----