On 15/01/2013 23:52, Daniel Holbert wrote:
In that scenario (if it exists) you could always use the build API (and
the shortcut red-stopsign buttons on TBPL) to effectively get what you want.
Killing running builds would mean needing to clobber all machines for
all platforms for that tree (unt
On 01/15/2013 01:20 PM, Gregory Szorc wrote:
> This seems to make sense. My only concern is if there is a scenario
> where you absolutely need to push without incurring a build (think merge
> commit where you don't have control over the previous commits). I'm not
> sure why we'd do that, so I'm inc
On 1/15/13 1:11 PM, Ehsan Akhgari wrote:
Hi all,
Currently, DONTBUILD only takes affect if it's set on the tip of the
changesets that you push. This can cause problems when merging between
different trees if the target tree is a full subset of the origin tree
(i.e., fast-forward merges in git t
Hi all,
Currently, DONTBUILD only takes affect if it's set on the tip of the
changesets that you push. This can cause problems when merging between
different trees if the target tree is a full subset of the origin tree
(i.e., fast-forward merges in git terminology) when the top-most changeset
is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 13/01/13 04:46, David Rajchenbach-Teller wrote:
> As a base for discussion, I have put together a small RFC based on
> promises: https://wiki.mozilla.org/RFC/TaskDependencies
You seem to be on the right track. You've probably already worke
On Tuesday, January 15, 2013 6:03:13 PM UTC+1, Boris Zbarsky wrote:
> On 1/15/13 11:57 AM, Jan Honza Odvarko wrote:
>
> > Is this expected behavior?
>
>
>
> Yes. Basically, objects and arrays now have the same enumeration
>
> behavior, and it's numeric properties in numeric order followed by
On 1/15/13 11:57 AM, Jan Honza Odvarko wrote:
Is this expected behavior?
Yes. Basically, objects and arrays now have the same enumeration
behavior, and it's numeric properties in numeric order followed by named
properties in addition order.
Note that that's the behavior Chrome implements a
Example:
var string = "{5: 5, 2: 2, 15: 15}";
var s = Components.utils.Sandbox("http://getfirebug.com";);
Components.utils.evalInSandbox("(" + string + ")", s);
---
Executing the previous code in Fx20 results with an object that has its
properties in the same order as defined in the |string|.
On Tue, Jan 15, 2013 at 03:19:42PM +, Neil wrote:
> Mike Hommey wrote:
>
> >On Tue, Jan 15, 2013 at 11:28:28AM +, Neil wrote:
> >
> >>Mike Hommey wrote:
> >>
> >>>It just maps anonymous memory (for big enough sizes)
> >>>
> >>Note that "big enough" is pretty large, I think 4MB in jemalloc'
Mike Hommey wrote:
On Tue, Jan 15, 2013 at 11:28:28AM +, Neil wrote:
Mike Hommey wrote:
It just maps anonymous memory (for big enough sizes)
Note that "big enough" is pretty large, I think 4MB in jemalloc's case.
It's 1MB as configured for us.
Out of interest, where is that se
Our NS_MIN/NS_MAX C++ templates have been removed and we're now using
std::min/std::max instead.
There's one exception: files under xpcom/ still use the old templates (now
renamed as XPCOM_MIN/MAX) because #include is not allowed in
some build configurations of xpcom. See bug 786533 for deta
On Fri, 2013-01-11 at 13:44 -0500, JP Rosevear wrote:
> On Fri, 2012-12-21 at 11:17 -0500, JP Rosevear wrote:
> > Hello all,
> >
> > As we prepare to enter 2013, I'd like to propose a set of goals for the
> > platform next year. These goals have had initial review by many
> > platform leaders and
On Tue, Jan 15, 2013 at 11:28:28AM +, Neil wrote:
> Mike Hommey wrote:
>
> >It just maps anonymous memory (for big enough sizes)
> >
> Note that "big enough" is pretty large, I think 4MB in jemalloc's
> case. (I don't know whether roc needs that much or not.)
It's 1MB as configured for us. An
Mike Hommey wrote:
It just maps anonymous memory (for big enough sizes)
Note that "big enough" is pretty large, I think 4MB in jemalloc's case.
(I don't know whether roc needs that much or not.)
--
Warning: May contain traces of nuts.
___
dev-platf
> --> Is there any change in xulrunner from 1.9.2 to 17.0.1 that I am missing
> which prevents the plugin to receive chrome content?
Never mind - a chrome path was missing a trailing slash in the chrome.manifest
;)
Paul
___
dev-platform mailing list
15 matches
Mail list logo
