On Thu, Feb 18, 2016 at 12:08 AM, Mike Lawther wrote:
> Is this something we can coordinate on?
Do you mean the Accept header? Not sure how Accept-Encoding makes sense here.
As for the MIME type to mention there, as I said in the bug I think we
should just ship image/apng (or video/apng though t
On 2016-02-17 01:59 PM, Gregory Szorc wrote:
> * You can now only run tasks if certain files changed.
This is *awesome*. Thank you!
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Is there a response to the criticism of Accept outlined here:
https://wiki.whatwg.org/wiki/Why_not_conneg#Negotiating_by_format
-Jeff
On Wed, Feb 17, 2016 at 6:08 PM, Mike Lawther wrote:
> Hi Mozilla developers!
>
> tl,dr; can Firefox send an Accept-Encoding heading for APNG?
>
> I'm an engineer
On 17/02/16 01:59 PM, Gregory Szorc wrote:
* You can now only run tasks if certain files changed. This opens the door
for drastic reduction in automation load via more intelligent scheduling of
tasks via in-tree configurations. (For the curious, relevant commits/files
are determined from a combin
On 18/02/16 07:45, Jeff Muizelaar wrote:
> Is there a response to the criticism of Accept outlined here:
> https://wiki.whatwg.org/wiki/Why_not_conneg#Negotiating_by_format
As Guardian of the Accept Header, that would be my question too.
Using Accept to detect APNG support will never be reliable
tl;dr: this will be a "Soft Close" to deal with glibc updates
As most of you know, upgrading glibc requires a reboot of each Linux host.
With so many hosts needing to be rebooted, there will be impacts on the
build and test machinery.
We fully expect the system to self-recover, but jobs in progre
6 matches
Mail list logo
