Output stipple in ~/.bzr.log

Robert Collins robert.collins at canonical.com
Wed Jun 24 06:53:56 BST 2009


On Wed, 2009-06-24 at 00:34 -0500, John Arbash Meinel wrote:
> -----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.

I'll file a bug for you if you like, for the duplicated messages; and
I'll prep a branch guarding them with -Dpack.

-Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090624/5d2fa918/attachment.pgp 


More information about the bazaar mailing list