call for testing: auto-refresh in Bazaar Explorer

[Maritza Mendez]

Based on that I'm guessing that sha1 is running.  I'm not complaining.
 The performance of other tools is not any better on this sort of use.
 What I love is that bzr is very quick for the kinds of things I do
every day.  If I see anything that seems unusually slow ill try to
collect the data.

Thanks
~M


On 9/5/09, John Arbash Meinel <john at arbash-meinel.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ian Clatworthy wrote:
>> Maritza Mendez wrote:
>>> Ian,
>>>
>>> Great idea!  Please make this optional with default=on.
>>
>> I'm happy to do that.
>>
>> I work on
>>> branches of various sizes from 2K to 20K files and up to a few hundred
>>> directories.  Usually I want status updated right away.  But if I have
>>> just moved a few hundred files (new libs or refactoring an old
>>> project) I might have to wait several minutes for status to update.
>>
>> If status takes several minutes to update, it's a bug. On the OOo tree
>> with 80K files, it only takes a few seconds at most for me.
>>
>> Ian C.
>>
>>
>
> Note that if we think a lot of content has changed, we might actually
> re-read the content and compute the sha1. That could take a long time.
>
> I don't think just renaming files would do that, but if the mtime was
> updated, it would.
>
> John
> =:->
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Cygwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkqiqVIACgkQJdeBCYSNAAP1iQCdEm0IDy5TlLA3eay4oHRWhNjf
> PDsAn3MZfwGhl6A4fdDi0kc0nc/xBy2F
> =jx6s
> -----END PGP SIGNATURE-----
>