My apologies to Pink. For future reference here is the email I sent to the team:
date Fri, Aug 29, 2008 at 2:45 PM subject default logging level change in chrome I've committed a change in ToT for chrome that: 1- Increases the default (minimum) login level from INFO to WARNING 2- Allows to specify any logging level in the command line with --log-level=n, with n = 0,1,2,3. Note that 0=INFO, 1=WARNING, 2=ERROR, 3= FATAL This decreases the amount of noise you see in the debugger. There is still quite a few noisy messages you see, mostly on the warning level. I would like to ask my fellow chromiunistas if they feel like increasing the default level one more notch. This change only affects chrome. Other modules are unit tests and shell_test are not affected. -cpu On Apr 22, 11:52 am, Evan Martin <[email protected]> wrote: > code.google.com is world-writable, so many of the docs there involve > user contributions. (E.g. the fedora build instructions.) > > > > On Wed, Apr 22, 2009 at 11:49 AM, Andrew Scherkus <[email protected]> > wrote: > > I might have missed this memo, but why are we splitting documentation across > > dev.chromium.org and code.google.com? > > Andrew > > > On Wed, Apr 22, 2009 at 11:37 AM, Evan Martin <[email protected]> wrote: > > >> Since Pinkerton just lost some hours to this and I did again: > >> The secret to getting LOG(INFO) to show is to pass --log-level=0 when you > >> run. > > >> I added this tohttp://code.google.com/p/chromium/wiki/LinuxDebugging > >> (which, by the way, has had a lot of content added since you last > >> looked). --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
