Oh, and until you can find someone to help you with the bot, the best course of action is probably to roll back your change. Sheriffbot on #webkit can help.
On Tue, Jun 1, 2010 at 1:10 PM, Jeremy Orlow <[email protected]> wrote: > On Tue, Jun 1, 2010 at 1:08 PM, Jeremy Orlow <[email protected]> wrote: > >> This mail is full of etiquette fail. First of all, you've now cross >> posted between webkit-dev and chromium-dev (using the @googlegroups address >> which was deprecated) so the majority of people who might respond can only >> do so to one list. You've also posted the real question (who do I contact >> about this builder) at the end...after people will have spent some time >> trying to figure out what you're talking about because you're using Chromium >> specific terminology. >> >> Anyhow, I've cc'ed the people who probably know and am bcc'ing webkit-dev. >> > > But apparently that's not allowed...so re-sending just to this list > manually. > > >> >> J >> >> On Tue, Jun 1, 2010 at 12:46 PM, Anton Muhin <[email protected]> wrote: >> >>> Looping in more people >>> >>> On Tue, Jun 1, 2010 at 3:40 PM, Anton Muhin <[email protected]> wrote: >>> > Dear webkitters, >>> > >>> > Commit queue just committed http://build.webkit.org/changes/11277 for >>> > me which includes Chromium DEPS roll (in WebKit). >>> > >>> > However things didn't go smooth: >>> > >>> http://build.webkit.org/builders/Chromium%20Win%20Release/builds/7199/steps/gclient/logs/stdio >>> > >>> > Most probably solution is to nuke >>> > >>> C:\WebKitBuildSlave\chromium-win-release\build\WebKit\chromium\base\third_party\dynamic_annotations >>> > , but how can I do it? >>> > >>> > yours, >>> > anton. >>> > >>> _______________________________________________ >>> webkit-dev mailing list >>> [email protected] >>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >>> >> >> >
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
