Re: [dev-servo] [stylo-team] Mozilla central backout support arriving to Servo later this week

"Backed out changeset 90036d4d378e (bug 17564) because gecko-side patch caused bustage on Windows. r=backout on a CLOSED TREE" I see issues in that: - Mentioning a Mercurial changeset hash when just a PR number is enough - Putting the reason of the backout directly in the title instead of the me

Re: [dev-servo] [stylo-team] Mozilla central backout support arriving to Servo later this week

On 19/06/2017 20:48, Lars Bergstrom wrote: tldr: If you see some PRs from the moz-servo-sync GitHub user with a priority of "treeclosed," it's because those must be landed into Servo ASAP to support Firefox backouts. Where do we file bugs on this tool? It creates a new PR that mentions the nu

Re: [dev-servo] [stylo-team] Mozilla central backout support arriving to Servo later this week

Anthony Ramine wrote: "Backed out changeset 90036d4d378e (bug 17564) because gecko-side patch caused bustage on Windows. r=backout on a CLOSED TREE" I see issues in that: - Mentioning a Mercurial changeset hash when just a PR number is enough this is true for the servo side. we need it on

Re: [dev-servo] [stylo-team] Mozilla central backout support arriving to Servo later this week

Simon Sapin wrote: On 19/06/2017 20:48, Lars Bergstrom wrote: tldr: If you see some PRs from the moz-servo-sync GitHub user with a priority of "treeclosed," it's because those must be landed into Servo ASAP to support Firefox backouts. Where do we file bugs on this tool? It creates a new PR