I've updated it with some information about MOZ_RAII.
On Mon, Sep 14, 2015 at 3:02 PM, Aaron Klotz wrote:
> Can you please update
> https://developer.mozilla.org/en-US/docs/Using_RAII_classes_in_Mozilla
> with this information?
>
> Thanks,
>
> Aaron
>
>
> On 9/12/2015 3:06 PM, Michael Layzell wr
The Bonsai server +infra is gone. Is there an alternative?
Is there a mercurial repository that has a unified history of
mozilla-central plus cvs history? Bonus if it also includes comm-central.
Phil
--
Philip Chee ,
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the sh
On 2015-09-15 11:08 AM, Philip Chee wrote:
> The Bonsai server +infra is gone. Is there an alternative?
>
> Is there a mercurial repository that has a unified history of
> mozilla-central plus cvs history? Bonus if it also includes comm-central.
>
> Phil
>
I'm pretty sure https://github.com/moz
On 9/15/2015 10:11 AM, Ben Hearsum wrote:
On 2015-09-15 11:08 AM, Philip Chee wrote:
The Bonsai server +infra is gone. Is there an alternative?
Is there a mercurial repository that has a unified history of
mozilla-central plus cvs history? Bonus if it also includes comm-central.
Phil
I'm pre
On 9/15/15 5:14 PM, Joshua Cranmer 🐧 wrote:
> On 9/15/2015 10:11 AM, Ben Hearsum wrote:
>> On 2015-09-15 11:08 AM, Philip Chee wrote:
>>> The Bonsai server +infra is gone. Is there an alternative?
>>>
>>> Is there a mercurial repository that has a unified history of
>>> mozilla-central plus cvs his
Mike Conley wrote:
From the passed in nsIWebProgress[1], you should be able to get at the
nsIDOMWindow, and from there, I *think* you can get to the nsIDocShell by
QI'ing the nsIWebProgress to an nsIInterfaceRequestor and then GetInterface'ing
nsIDocShell. I haven't tried this, but I'm reason
On 9/15/15 11:11 AM, Ben Hearsum wrote:
I'm pretty sure https://github.com/mozilla/gecko-dev has full history.
Though note that it doesn't have working blame for a lot of files in our
source tree (and especially the ones you'd _want_ to get blame for, in
my experience), so it's of pretty limi
Joshua Cranmer 🐧 wrote:
There is no git or mercurial repository that contains the full history
of mozilla CVS. Slightly unsurprising, since the full history of
mozilla CVS actually breaks most conversion tools.
Even "CVS moved" files throw them a loop, I tried looking for blame for
some code
On 9/15/2015 10:53 AM, Boris Zbarsky wrote:
On 9/15/15 11:11 AM, Ben Hearsum wrote:
I'm pretty sure https://github.com/mozilla/gecko-dev has full history.
Though note that it doesn't have working blame for a lot of files in
our source tree (and especially the ones you'd _want_ to get blame
f
On 09/15/2015 06:53 PM, Boris Zbarsky wrote:
On 9/15/15 11:11 AM, Ben Hearsum wrote:
I'm pretty sure https://github.com/mozilla/gecko-dev has full history.
Though note that it doesn't have working blame for a lot of files in our source
tree (and especially the ones you'd _want_ to get blame f
On Tue, Sep 15, 2015 at 8:08 AM, Philip Chee wrote:
> The Bonsai server +infra is gone. Is there an alternative?
>
> Is there a mercurial repository that has a unified history of
> mozilla-central plus cvs history? Bonus if it also includes comm-central.
>
https://hg.mozilla.org/users/gszorc_moz
Hi all,
For some intermittent leaks, it's not at all clear where the leaked objects
are coming from, especially for objects that are widely used across the
codebase. Bug 1196430 added the ability for our leak checking mechanism to
track allocation stacks of objects and to print said stacks for le
On Mon, Aug 31, 2015 at 1:11 PM, Josh Matthews
wrote:
> Servo is particularly interested in getting usage data for just about
> every DOM API that exists in Gecko. We'd like to use this to inform our
> priorities for implementing missing features in Servo. Is this a realistic
> request? If not, w
On Mon, Aug 24, 2015 at 8:40 PM, Karl Dubost wrote:
> Is there a plan for a step by step guide on how to
>
> 1. implement a new counter
>
I plan on writing some documentation for
https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Adding_a_new_Telemetry_probe
very soon.
> 2. access th
This looks super useful - thanks Nathan! Tooling like this is critical to
helping us get to the bottom of intermittent nastiness.
On Tue, Sep 15, 2015 at 1:32 PM, Nathan Froyd wrote:
> Hi all,
>
> For some intermittent leaks, it's not at all clear where the leaked objects
> are coming from, espe
Apparently Bugzilla 2fa breaks the weird cookie authentication method that
git-bz-moz and bzexport use. I think I've read that this is a bugzilla bug,
but in the meanwhile I've been working on making git-bz-moz use the
Bugzilla backend of bexport, which is less hacky and supports using API
keys for
Oh, and another thing I meant to mention that seems underused: if you are
using git-bz-moz, the |git apply| command is pretty handy. You can do |git
apply 12345| where 12345 is a bug number, and it will prompt you for each
non-obsolete patch attachment and apply it if you want it.
Andrew
On Tue,
Sorry, the command is actually |git bz apply 12345| as you probably figured
out.
Andrew
On Tue, Sep 15, 2015 at 2:40 PM, Andrew McCreight
wrote:
> Oh, and another thing I meant to mention that seems underused: if you are
> using git-bz-moz, the |git apply| command is pretty handy. You can do |g
The Mercurial extensions to interact with Bugzilla -- bzexport and the like --
have been updated to handle 2fa details. No need to add API key support
yourself, or use some sketchy dude's user-repo fix for the issue! ;-) (As at
least three people have considered, two people have actually done
And as of a few seconds ago `mach mercurial-setup` (on just inbound so far)
will guide you through defining an API key. It will also purge your hgrc of
the legacy auth credentials, which won't work with 2FA.
Bug 1200461 if there are any issues.
On Tue, Sep 15, 2015 at 2:52 PM, Jeff Walden wrote:
On 30/12/14 09:40 PM, Francois Marier wrote:
> Summary: Allow web authors to add integrity checks to sub-resources.
>
> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=992096
>
> Spec: http://www.w3.org/TR/SRI/
>
> Platforms: all
>
> Estimated or target release: Q1 of 2015
>
> Preference beh
On 15/09/2015 23:53, Boris Zbarsky wrote:
> On 9/15/15 11:11 AM, Ben Hearsum wrote:
>> I'm pretty sure https://github.com/mozilla/gecko-dev has full history.
Thanks to everyone for your suggestions.
> Though note that it doesn't have working blame for a lot of files in our
> source tree (and esp
22 matches
Mail list logo
