lla.org/listinfo/dev-servo
--
David Rajchenbach-Teller, PhD
Performance Team, Mozilla
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
do better. Specifically, I'm interested in moving
> to isolated event queues per document, then doing round-robin event
> processing on each on in an eTLD group. That would make the script event
> loop look something like this:
--
David Rajchenbach-Teller, PhD
Performance Team, M
I just attempted to build Servo on a new computer, only to end with the
following output:
$ ./mach bootstrap
Running virtualenv with interpreter /opt/local/bin/python2.7
New python executable in
/Users/david/Documents/Code/servo/python/_virtualenv/bin/python
Installing setuptools, pip, wheel...don
I'll give a quick (unscheduled) talk about Telemetry for Servo today at
11h10 in Northern E4.
Cheers,
David
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Very good point. In Gecko-land, some teams use multi-line commit
messages as documentation and my experience shows that it's very useful.
Cheers,
David
On 03/02/16 20:21, Boris Zbarsky wrote:
> On 2/3/16 1:46 PM, Josh Matthews wrote:
>> Nikki asked for suggestions for how to review code, so here
In Gecko, I have taken the habit of requesting long messages when the
patch is not self-contained. Plus, I am currently working on bugs that
would have been much easier to puzzle out if we (well, if I) had
explained in the long message why some changes were made.
In other words, +1 for requesting
6 matches
Mail list logo
