{"push_id":1182093087,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"51b08d511e8b42eace59588a7eea73c4d21d222d","before":"cc6f5f6ce1daca51f475764a3e4fa9420cafcefa","commits":[{"sha":"51b08d511e8b42eace59588a7eea73c4d21d222d","author":{"name":"Brad Fitzpatrick","email":"9b57cd4de34ef5e00ba5b6ee67d7b6e836d0dbaa@golang.org"},"message":"net/http: be consistent about spelling of HTTP/1.x\n\nThere was only one use of \"HTTP/1.n\" compared to \"HTTP/1.x\":\n\nh2_bundle.go://   \"Just as in HTTP/1.x, header field names are strings of ASCII\nhttputil/dump.go:// DumpRequest returns the given request in its HTTP/1.x wire\nhttputil/dump.go:// intact. HTTP/2 requests are dumped in HTTP/1.x form, not in their\nresponse.go:// Write writes r to w in the HTTP/1.x server response format,\nserver.go:      // Request.Body. For HTTP/1.x requests, handlers should read any\nserver.go:// The default HTTP/1.x and HTTP/2 ResponseWriter implementations\nserver.go:// The default ResponseWriter for HTTP/1.x connections supports\nserver.go:// http1ServerSupportsRequest reports whether Go's HTTP/1.x server\nserver.go:      // about HTTP/1.x Handlers concurrently reading and writing, like\nserver.go:      // HTTP/1.x from here on.\ntransport.go:   return fmt.Errorf(\"net/http: HTTP/1.x transport connection broken: %v\", err)\n\nBe consistent.\n\nChange-Id: I93c4c873e500f51af2b4762055e22f5487a625ac\nReviewed-on: https://go-review.googlesource.com/24610\nReviewed-by: Andrew Gerrand <adg@golang.org>","distinct":true,"url":"https://api.github.com/repos/mk0x9/go/commits/51b08d511e8b42eace59588a7eea73c4d21d222d"}]}
{"actor":{"display_login":"mk0x9"}}