[protobuf] Re: Issue 485 in protobuf: ByteString should be Serializable

Comment #4 on issue 485 by xiaof...@google.com: ByteString should be Serializable https://code.google.com/p/protobuf/issues/detail?id=485 Hi fizbin, Thanks for providing the patch. Can you submit the patch to our new github site: https://github.com/google/protobuf/pulls and sign this

[protobuf] Re: Issue 485 in protobuf: ByteString should be Serializable

Comment #3 on issue 485 by vi...@umich.edu: ByteString should be Serializable http://code.google.com/p/protobuf/issues/detail?id=485 Alongside serialization... The internal usage of RopeByteString (and RopeInputStream) is particularly interesting. It would be very handy if ByteString

[protobuf] Re: Issue 485 in protobuf: ByteString should be Serializable

Comment #2 on issue 485 by fiz...@gmail.com: ByteString should be Serializable http://code.google.com/p/protobuf/issues/detail?id=485 Obviously in the patch I meant the exception text to read not to be serialized instead of the nonsensical not to serialized. -- You received this message

[protobuf] Re: Issue 485 in protobuf: ByteString should be Serializable

Updates: Status: Accepted Owner: xiaof...@google.com Labels: -Type-Defect Type-Patch Comment #1 on issue 485 by xiaof...@google.com: ByteString should be Serializable http://code.google.com/p/protobuf/issues/detail?id=485 (No comment was entered for this change.) --