protobuf - Protocol Buffers - Google's data interchange format

	Commit message (Collapse)	Author	Age	Files	Lines
*	Down-integrate from google3.	Feng Xiao	2018-08-08	1	-2/+2
\|
*	Integrated internal changes from Google	Adam Cozzette	2018-03-13	1	-5/+2
\|
*	Down-integrate from google3.	Feng Xiao	2017-03-29	1	-1/+1
\|
*	Integrated internal changes from Google	Adam Cozzette	2016-11-17	1	-1/+1
\|
*	Down integrate from Google internal.	Jisi Liu	2016-04-28	1	-6/+7
\|
*	Down-integrate from internal code base.	Feng Xiao	2015-12-11	1	-0/+8
\|
*	Down-integrate from google3.	Feng Xiao	2015-08-22	1	-0/+1
\|
*	Down-integrate from internal code base (C++ maps support).	Feng Xiao	2014-11-14	1	-3/+3
\|
*	Down-integrate from internal code base.	Feng Xiao	2014-11-10	1	-115/+9
\|
*	Adds more checks before deleting temporary files.	Feng Xiao	2014-11-08	1	-1/+3
\|
*	Replace links to code.google.com/protobuf with ↵	Feng Xiao	2014-10-01	1	-1/+1
\| \| \| \|	developers.google.com/protocol-buffers
*	down integrate to svn	jieluo@google.com	2014-07-18	1	-19/+36
\|
*	Integrate recent changes from Google-internal code tree. See CHANGES.txt	kenton@google.com	2009-04-25	1	-0/+28
\| \| \| \| \|	for details.
*	* Avoid using pushd/popd in generate_descriptor_proto.sh because they are	kenton@google.com	2008-12-02	1	-0/+12
\| \| \| \| \| \| \| \| \| \|	bash-only features, and /bin/sh is not a symlink to bash on all systems. * If an input file is a Windows absolute path (e.g. "C:\foo\bar.proto") and the import path only contains "." (or contains "." but does not contain the file), protoc incorrectly thought that the file was under ".", because it thought that the path was relative (since it didn't start with a slash). This has been fixed.
*	Integrate changes from internal Google-internal branch.	kenton@google.com	2008-09-24	1	-10/+24
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	General * License changed from Apache 2.0 to New BSD. * It is now possible to define custom "options", which are basically annotations which may be placed on definitions in a .proto file. For example, you might define a field option called "foo" like so: import "google/protobuf/descriptor.proto" extend google.protobuf.FieldOptions { optional string foo = 12345; } Then you annotate a field using the "foo" option: message MyMessage { optional int32 some_field = 1 [(foo) = "bar"] } The value of this option is then visible via the message's Descriptor: const FieldDescriptor* field = MyMessage::descriptor()->FindFieldByName("some_field"); assert(field->options().GetExtension(foo) == "bar"); This feature has been implemented and tested in C++ and Java. Other languages may or may not need to do extra work to support custom options, depending on how they construct descriptors. C++ * Fixed some GCC warnings that only occur when using -pedantic. * Improved static initialization code, making ordering more predictable among other things. * TextFormat will no longer accept messages which contain multiple instances of a singular field. Previously, the latter instance would overwrite the former. * Now works on systems that don't have hash_map. Python * Strings now use the "unicode" type rather than the "str" type. String fields may still be assigned ASCII "str" values; they will automatically be converted. * Adding a property to an object representing a repeated field now raises an exception. For example: # No longer works (and never should have). message.some_repeated_field.foo = 1
*	Allow trailing slashes in --proto_path mappings.	temporal	2008-07-16	1	-0/+7
\| \| \| \| \|	Patch by Kevin Ko <kevin.s.ko@gmail.com>.
*	Initial checkin.	temporal	2008-07-10	1	-0/+539