Output stipple in ~/.bzr.log

[John Arbash Meinel]

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

Martin Pool wrote:
> 2009/6/24 Robert Collins <robert.collins at canonical.com>:
>> John, do we need the
>> 111.114  creating new compressed block on-the-fly in 0.000s 219713 bytes
>> => 9572 bytes
>> 111.115  stripping trailing bytes from groupcompress block 219713 =>
>> 9361
>>
>>
>> output ? its really very verbose..
> 
> Yes, in things that merge to trunk please guard them with a debug_flag
> unless there's a really good reason otherwise.
> 

I'm fine with that. Though looking at the logs it does show stuff like:
79.484  stripping trailing bytes from groupcompress block 2187156 => 5719
79.491  creating new compressed block on-the-fly in 0.004s 2187156 bytes
=> 56660 bytes
79.500  creating new compressed block on-the-fly in 0.004s 2187156 bytes
=> 56885 bytes

And I have to wondre why it is reading the same source content 3 times
in short succession and giving a different bit of content each time.


And honestly, I see that a *lot* in the log...

But I'm sure it was just a mutter() that got left in.

John
=:->

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

iEYEARECAAYFAkpBuvYACgkQJdeBCYSNAAMpOQCgyPNQUDEQcEJplF4pMGP24iWu
KGUAmwVfcSGODfBSfNkTG26OeyY/WOI2
=Zm0j
-----END PGP SIGNATURE-----