protobuf - Protocol Buffers - Google's data interchange format

	Commit message (Collapse)	Author	Age	Files	Lines
*	Support ToString in RepeatedField and MapField.	Jon Skeet	2015-10-01	1	-0/+16
\| \| \| \| \| \|	This changes how we approach JSON formatting in general - instead of looking at the field a value came from, we just look at the type of the value. It's possible this could be slightly inefficient, but if we start caring about JSON performance deeply, we'll probably want to rewrite all of this anyway. It's definitely simpler this way. When we support dynamic messages, we'll need to modify JsonFormatter to handle enum values, as they won't come be "real" .NET enums at that point. It shouldn't be hard to do though.
*	Tidying up - fix a bunch of TODOs and remove outdated ones.	Jon Skeet	2015-08-08	1	-4/+2
\|
*	Document everything, and turn on errors if we fail to document anything in ↵	Jon Skeet	2015-08-04	1	-2/+109
\| \| \| \|	the future.
*	More freezing tidy-up; generated code in next commit.	Jon Skeet	2015-07-30	1	-2/+1
\|
*	Minor bits of left-over frozenness.	Jon Skeet	2015-07-30	1	-1/+0
\|
*	remove the freeze API	Jan Tattermusch	2015-07-29	1	-26/+3
\|
*	First attempt at using profile 259 for Google.Protobuf.	Jon Skeet	2015-07-27	1	-4/+6
\| \| \| \| \| \| \| \|	This requires .NET 4.5, and there are a few compatibility changes required around reflection. Creating a PR from this to see how our CI systems handle it. Will want to add more documentation, validation and probably tests before merging. This is in aid of issue #590.
*	First pass at the big rename from ProtocolBuffers to Google.Protobuf.	Jon Skeet	2015-07-17	1	-0/+470
	We'll see what I've missed when CI fails...