On Tue, Sep 22, 2009 at 6:15 PM, Dimitri Glazkov <dglaz...@chromium.org> wrote:
> I think this is the key point. This is a temporary situation. The
> biggest issue is that _we_ as a team are the key aggravators of the
> issue. Let's solve it by being more diligent on the upstream side,
> because that's where we'll live once webkit is decoupled from
> chromium.
Sorry to cross threads, but we can integrate the commit-queue with the
chromium try servers so it won't land patches that break the canary.
That might be a good automated solution.
Adam
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
