On 08/02/17 22:31, Jack Moffitt wrote:
Let's allow until Friday afternoon for feedback to come in, but I
don't think it makes sense to delay this decision.
I approved https://github.com/servo/servo/pull/15447 and it has already
landed. Oh well.
I’ve pushed a new branch to https://github.com/
I'm not against the decision if we are willing to revert it in the future
(which is why I didn't reply immediately following your reply), but I have a
few things to say nonetheless.
> Le 8 févr. 2017 à 19:42, Bobby Holley a écrit :
>
> On Wed, Feb 8, 2017 at 2:28 AM, Anthony Ramine wrote:
>
On Thu, Feb 9, 2017 at 10:51 AM, Anthony Ramine wrote:
> In general, I posit that Mozilla completely, utterly, lost against V8 in
> the embedded department in a huge part because of this mono-repository
> thing where everything is muddled together.
>
(Sorry for going offtopic, but I don't think
I do know that there was once a discussion between the folks behind
greenkeeper.io and Rustaceans to support Rust/crates.io as well.
I can check with those people to see if that went anywhere or what would
be needed to make it happen.
On Wed, Feb 08, 2017 at 06:23:47PM +0100, David Bruant wrote:
On 09/02/17 09:51, Anthony Ramine wrote:
I haven't split it out yet, because I'm still hoping that the
outcome of this discussion is that I won't have to. The unified
code changes are in part 3 of
https://bugzilla.mozilla.org/show_bug.cgi?id=1336646
How does the discussion mean you don't have
WPT still has its own repo; the Servo repo just does an occasional
bidirectional sync. The equivalent for rust-selectors would be if the
rust-selectors repo was kept and just occasionally synced with Servo (like
Servo is doing for M-C, anyway).
On Thu, Feb 9, 2017 at 8:21 AM James Graham wrote:
On 09/02/17 16:18, Michael Howell wrote:
WPT still has its own repo; the Servo repo just does an occasional
bidirectional sync. The equivalent for rust-selectors would be if the
rust-selectors repo was kept and just occasionally synced with Servo (like
Servo is doing for M-C, anyway).
Sure, but
Could we do the same thing for rust-selectors? And should we?
On Thu, Feb 9, 2017 at 9:27 AM James Graham wrote:
> On 09/02/17 16:18, Michael Howell wrote:
> > WPT still has its own repo; the Servo repo just does an occasional
> > bidirectional sync. The equivalent for rust-selectors would be if
> In general, I posit that Mozilla completely, utterly, lost against V8 in the
> embedded department in a huge part because of this mono-repository thing
> where everything is muddled together.
I don't think anyone is disagreeing with you on this point. The plan
is as it always has been - to spl
I think the complexity of the wpt-style setup is overkill, but I think
we could do something to alleviate the community participation issue.
We could perhaps keep the rust-selectors repo around and following the
Servo in-tree one. PRs could still be done by external contributors
the rust-selectors
> On Feb 9, 2017, at 01:51, Anthony Ramine wrote:
>
> I'm not against the decision if we are willing to revert it in the future
> (which is why I didn't reply immediately following your reply), but I have a
> few things to say nonetheless.
>
>> Le 8 févr. 2017 à 19:42, Bobby Holley a écrit
11 matches
Mail list logo
