5. Moving forward, reviewers and committers take care not to re-add
expectations when committing pending patches. While I expect svn will warn
in most cases, I doubt that it will catch everything.
6. "Won't fix" any bugs related to chromium-cg results.
Stephen.
On Wed, Jan 4, 2012 at 9:10 AM, El
The Chromium port uses v8 for all platforms. Is that not what you would
like?
Stephen.
On Mon, Jan 30, 2012 at 7:41 PM, Ryan Ackley wrote:
> I want to use Webkit for a project I'm working on but I would prefer
> the v8 JavaScript engine for a variety of reasons. I did see that
> there was a Qt
There is a significant practical problem to "turn the tree red and work
with someone to rebaseline the tests". It takes multiple hours for some
bots to build and test a given patch. That means, at any moment, you will
have maybe tens and in some cases hundreds of failing tests associated with
some
Ideally WebKit would avoid casts by consistently using either double or
floats everywhere a floating point representation is needed. I don't think
it's as simple as adding a typedef, but maybe it is. In any event it would
have to be spelled out in the style guide.
My gut feeling is that floats are
On Wed, Jul 11, 2012 at 6:07 PM, Alec Flett wrote:
> I absolutely do not buy that the "cost" of keeping comments up to date and
> the "cost" of out-of-date comments outweighs the benefits - that has NEVER
> been my experience and if anything the benefits of comments grow as the
> number of people
On Thu, Jul 12, 2012 at 3:44 PM, Dirk Pranke wrote:
> On Thu, Jul 12, 2012 at 10:53 AM, Ryosuke Niwa wrote:
> > On Thu, Jul 12, 2012 at 10:43 AM, Stephen Chenney >
> > wrote:
> >>
> >> As several people have shown, it is quite easy to come up with a
On Thu, Jul 12, 2012 at 5:31 PM, Maciej Stachowiak wrote:
>
> On Jul 12, 2012, at 1:47 PM, Stephen Chenney
> wrote:
>
>
>
> On Thu, Jul 12, 2012 at 3:44 PM, Dirk Pranke wrote:
>
>> On Thu, Jul 12, 2012 at 10:53 AM, Ryosuke Niwa wrote:
>> > On Thu, Ju
On Thu, Aug 16, 2012 at 6:15 PM, Ryosuke Niwa wrote:
> On Thu, Aug 16, 2012 at 3:04 PM, Dirk Pranke wrote:
>
>> On Thu, Aug 16, 2012 at 2:23 PM, Ryosuke Niwa wrote:
>> > Like Filip, I'm extremely concerned about the prospect of us introducing
>> > yet-another-way-of-doing-things, and not be abl
I also like this idea. I particularly like the side effect of making it
clear when a patch is modifying a test result that is itself not
necessarily up to date.
I suggest a policy that says you must rebaseline a test before committing a
patch that would change that test (if the test is marked as n
I second the principle. I ran into this kind of code pattern recently in
fonts and was unnerved by the thought of a mutable pointer emerging from a
const method.
I am not at all certain that we can simply make the change without some
heavy refactoring. On the one hand, there are some long const-ne
On Thu, Jan 3, 2013 at 3:14 PM, Peter Kasting wrote:
> On Thu, Jan 3, 2013 at 11:36 AM, Shawn Singh wrote:
>
>> Cons of making a separate vector class:
>> - "offsets" are sometimes treated as relative point locations, and
>> other times treated as vectors that can be added to points. Deciding
I am making a pass to mark Chromium-specific bugs as WontFix in WebKit
while adding Chromium bugs as appropriate. This is generating lots of
email, which is unfortunate but unavoidable.
Should you get notification of a bug you care about, and wish to track it
in Chromium, please go to crbug.com an
12 matches
Mail list logo
