Damien Neil a7cbd06b9b cmd/protoc-gen-go: don't chain public imports ... Consider the case: a.proto publicly imports b.proto b.proto publicly imports c.proto Should a.pb.go include symbols defined in c.pb.go? Historically, it has not. As of #155677, it does. Regardless of which behavior is preferable, #155677 produces broken code in some common situations: If a.proto also publicly imports c.proto, we now generate two copies of the forwarding decls for that file. Restore the pre-#155677 behavior to avoid this breakage. Change-Id: I283600b3be19eac2c3b3c14233bb69fa64661581 Reviewed-on: https://go-review.googlesource.com/c/156348 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>		2019-01-07 23:17:30 +00:00
..
protoc-gen-go	cmd/protoc-gen-go: don't chain public imports	2019-01-07 23:17:30 +00:00
protoc-gen-go-grpc	cmd/protoc-gen-go-grpc: regenerate golden file	2019-01-05 01:25:02 +00:00