On Wed, Aug 5, 2009 at 2:49 PM, Peter Kasting <[email protected]> wrote:
> On Wed, Aug 5, 2009 at 2:45 PM, Tim Steele <[email protected]> wrote: > >> A constant place to go looking for this would make it easier, at least in >> my opinion. Like right now I don't know what's up with Chromium Mac >> (valgrind) or Webkit dbg (1&2) to name a few; they're red but the tree is >> open. > > > If you ever see a case like this, go ahead and close the tree yourself > until you get an explanation for every bit of redness. Then put the > explanation into the tree status. > > I know people hate having the tree closed, but we need to be hard-nosed > about closing it for _anything_ red. > This is the approach I default to, because I'm just pessimistic by nature :) I think the one time I closed the tree in the last 5 months was one of these cases, and I was scolded because it wasn't necessary, so in true Pavlovian fashion I'm now afraid to do it again. Nevertheless, dually noted! Maybe just a way to have a bit more verbose tree status? A <details> link that would just expand below the status header to show the rest of the text? I'll tell you what, I'll build up a bit more experience as a sheriff myself before I start making grand plans to redesign things :) > > PK > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
