{"push_id":545136484,"size":4,"distinct_size":1,"ref":"refs/heads/incremental_deployment","head":"fbe4f9340c29168e420ad9b114f5ca161e6203ad","before":"22e4299f5b2d9e3d21177622c5192d806d976e09","commits":[{"sha":"52b15187c291a9a9e4aa2fa7146693d7487899f4","author":{"email":"73675debcd8a436be48ec22211dcf44fe0df0a64@links.org","name":"Ben Laurie"},"message":"Refer to external doc, broaden \"gossip\" mechanisms.","distinct":false,"url":"https://api.github.com/repos/eranmes/certificate-transparency-rfcs/commits/52b15187c291a9a9e4aa2fa7146693d7487899f4"},{"sha":"adbb9942a0a05f89c1dd4f2dde9c9d58ea5575b6","author":{"email":"73675debcd8a436be48ec22211dcf44fe0df0a64@links.org","name":"Ben Laurie"},"message":"Typo.","distinct":false,"url":"https://api.github.com/repos/eranmes/certificate-transparency-rfcs/commits/adbb9942a0a05f89c1dd4f2dde9c9d58ea5575b6"},{"sha":"cddc25c97f3d4129b297382b39c86e2d106c7c43","author":{"email":"ae86a985811ad650849e18e2730905d68b96b36d@google.com","name":"Eran"},"message":"Ticket 42: Clarifying what overly redacted means and how TLS clients could check for it.","distinct":false,"url":"https://api.github.com/repos/eranmes/certificate-transparency-rfcs/commits/cddc25c97f3d4129b297382b39c86e2d106c7c43"},{"sha":"fbe4f9340c29168e420ad9b114f5ca161e6203ad","author":{"email":"ae86a985811ad650849e18e2730905d68b96b36d@google.com","name":"Eran"},"message":"Ticket 31: Clarify treatment of certificates without SCTs\n\nAs we do not desire to specify client behaviour, simply indicate that\ncertificates not accompanied by an SCT are not compliant (it's up to\nthe client to decide what to do with non-compliant certificates).","distinct":true,"url":"https://api.github.com/repos/eranmes/certificate-transparency-rfcs/commits/fbe4f9340c29168e420ad9b114f5ca161e6203ad"}]}