protobuf - Protocol Buffers – Google’s data interchange format

	Commit message (Collapse)	Author	Age
*	Merge from Google internal for 3.4 release	Jisi Liu	2017-07-18
\|
*	Down-integrate from google3.	Feng Xiao	2017-03-29
\|
*	Changed go_package for plugin.proto.	Josh Haberman	2017-03-15
\| \| \| \|	For more info see: https://github.com/google/protobuf/issues/1289
*	Add version number to plugin protocol.	Feng Xiao	2016-12-05
\|
*	Down integrate from Google internal branch for C++ and Java.	Jisi Liu	2015-02-28
\| \| \| \| \| \| \| \|	- Maps for C++ lite - C++ Arena optimizations. - Java Lite runtime code size optimization. Change-Id: I7537a4357c1cb385d23f9e8aa7ffdfeefe079f13
*	Down-integrate from internal code base.	Feng Xiao	2014-11-10
\|
*	Replace links to code.google.com/protobuf with ↵	Feng Xiao	2014-10-01
\| \| \| \|	developers.google.com/protocol-buffers
*	Add java options to plugin proto and rollback the r450	liujisi@google.com	2012-12-05
\|
*	Submit recent changes from internal branch. See CHANGES.txt for more details.	liujisi@google.com	2010-11-02
\|
*	Tweak doc comments.	kenton@google.com	2010-01-08
\|
*	Refactor the way output is handled in CommandLineInterface -- now it will be ↵	kenton@google.com	2009-12-23
\| \| \| \|	stored in-memory until all code generators have completed, then dumped to disk all at once. While this means that protoc uses more memory, the code is much simpler, and handles insertions much faster. Also, this made it easier to implement a useful feature: insertions will be indented to match the insertion point line. Therefore, when inserting into Python code, you don't have to figure out how much to indent your inserted code. The refactoring should also make it easier to implement output-to-jar at some point.
*	Mark plugins as experimental for now.	kenton@google.com	2009-12-22
\|
*	Commit missing files from r251. Sigh.	kenton@google.com	2009-12-18