-- Forwarded message --
From: "Lars Bergstrom"
Date: Dec 17, 2015 11:26 AM
Subject: Re: [dev-servo] Fwd: Profile directory (Re: IndexDB project)
To: "Josh Matthews"
Cc:
How do you see this (profile stuff) in relation to startup caches? I
need to implement one really badly for And
On Thu, Dec 17, 2015 at 5:08 PM, Lars Bergstrom
wrote:
> - How do we handle commit access? Having the upstream maintainers
> (none of whom might be current Gecko peers) correctly identified and
> doing reviews in bugzilla to ensure m-c pushes can be upstreamed seems
> challenging.
>
Auto-upstrea
Thanks for doing this investigation, Valentin!
I'm a little bit worried about the mechanics of auto-upstreaming:
- How do we handle commit access? Having the upstream maintainers
(none of whom might be current Gecko peers) correctly identified and
doing reviews in bugzilla to ensure m-c pushes can
On 17/12/15 23:04, Valentin Gosu wrote:
From what I understand servo's mach has a command for two-way sync between
web-platform-tests and upstream.
It does, but let's be clear that the implementation there isn't end-user
quality and is simplified byd specific policies in web-platform-tests
I had a long conversation about the two-way sync stuff at Orlando with Alex
and some of the Servo folks.
We concluded that, long-term, we need to let Gecko hackers commit to the
vendored code and have that code automatically upstreamed. Similarly,
upstream fixes need to be automatically merged int
Hi folks,
I just wanted to share some notes on using Cargo in Gecko. One of the
requirements was vendoring packages in tree. It turns out I was able to do
that with a .cargo/config file in the scope of the rust directory, which
defines the paths for dependencies, and [http] timeout = 0, which prev
On 2015-12-17 12:53 PM, Simon Sapin wrote:
On 17/12/15 17:09, Josh Matthews wrote:
Right, I know there are expected conventions. My previous suggestion was
an attempt to provide a mechanism to allow testing persistence between
sessions without actually committing to any of the work involved in
c
On 17/12/15 17:09, Josh Matthews wrote:
Right, I know there are expected conventions. My previous suggestion was
an attempt to provide a mechanism to allow testing persistence between
sessions without actually committing to any of the work involved in
creating a proper setup for persistent profil
Right, I know there are expected conventions. My previous suggestion was
an attempt to provide a mechanism to allow testing persistence between
sessions without actually committing to any of the work involved in
creating a proper setup for persistent profiles. That feels like a
distraction to m
-- Forwarded message --
From: "Simon Sapin"
Date: Dec 17, 2015 11:06 AM
Subject: Profile directory (Re: [dev-servo] IndexDB project)
To: "Josh Matthews"
Cc:
On 17/12/15 14:43, Josh Matthews wrote:
> We still don't have any persistent storage in Servo, such as a profile
> folder.
We still don't have any persistent storage in Servo, such as a profile
folder. I would be fine with adding a command line option to provide a
profile directory, or creating a temporary directory if none is provided.
On 2015-12-17 3:17 AM, Jan Jansen wrote:
Hi Shing,
I start working on write a
Hi Shing,
I start working on write a wrapper for SQLite 4. This are my first bindings, so
I had some trouble with selecting correct types.
Then stop working on it the last weeks. I had lot of work for my current therm.
With the beginning of winter vacations I have more time.
I didn't want to
Hi
I mentioned my interest to work on github sometimes ago. I think it is possible
split work.
Regards,
Jan
> On 16 Dec 2015, at 11:13, Shing Lyu wrote:
>
> Haha, I don't really need to choose IndexDB.
>
> If you guys think IndexDB is not valuable for Servo, can you suggest
> something I ca
13 matches
Mail list logo
