{"push_id":943528851,"size":2,"distinct_size":2,"ref":"refs/heads/inbound","head":"113252b726989a8bdf9f86d54a6a9c254f406160","before":"398d96e8e543c17ec534442afce6948adb85b51d","commits":[{"sha":"97affffb420bd35c0ab95d937fc16723638a52bd","author":{"email":"790fae358fdaa0da689adfd65aa45171adc5f989@mozilla.com","name":"Ehsan Akhgari"},"message":"Bug 1240372 - Don't OOM crash in nsDocumentEncoder::EncodeToStringWithMaxLength() when the string buffer allocation fails; r=bzbarsky","distinct":true,"url":"https://api.github.com/repos/mozilla/gecko-dev/commits/97affffb420bd35c0ab95d937fc16723638a52bd"},{"sha":"113252b726989a8bdf9f86d54a6a9c254f406160","author":{"email":"a359ebe66ae7fdfea59b189140ed9b92368acfba@mozilla.com","name":"David Keeler"},"message":"bug 1239455 - rework telemetry for SHA-1 certificates to reflect possible policy states r=Cykesiopka,mgoodwin,rbarnes\n\nBefore this patch, we were measuring where SHA-1 was being used in TLS\ncertificates: nowhere, in end-entities, in intermediates, or in both. However,\nthe possible SHA-1 policies don't differentiate between end-entities and\nintermediates and instead depended on whether or not each certificate has a\nnotBefore value after 2015 (i.e. >= 0:00:00 1 January 2016 UTC). We need to\ngather telemetry on the possible policy configurations.\n\n--HG--\nextra : rebase_source : 301c821c8de16ffb924cd198dd0a4d3139536019","distinct":true,"url":"https://api.github.com/repos/mozilla/gecko-dev/commits/113252b726989a8bdf9f86d54a6a9c254f406160"}]}