Update client-side sync.proto file so that it is in sync

Update client-side sync.proto file so that it is in sync with the
server-side version

BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=221910

[pval...(no longer on Chromium), 2013-09-06 00:55:13]

These files got out of sync (server-side modified first), so this CL should
correct that. Full disclosure: one of the two modifications was my fault. :-P

[rlarocque, 2013-09-06 21:56:43]

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto
File sync/protocol/sync.proto (right):

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto#newc...
sync/protocol/sync.proto:646: optional ClearUserDataMessage clear_user_data = 9;
I guess I'm not opposed to this change, but why did it happen?

Could we use the deprecated option here?

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto#newc...
sync/protocol/sync.proto:680: // Id of the uploaded crash
Add a period?

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto#newc...
sync/protocol/sync.proto:683: // Time that the crash occurred
period?

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto#newc...
sync/protocol/sync.proto:687: // Proto to be written in its entirety to the
debug info log
period?

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto#newc...
sync/protocol/sync.proto:689: // Hash of the crashing calltack.
typo: calltack.

[pval...(no longer on Chromium), 2013-09-06 22:08:58]

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto
File sync/protocol/sync.proto (right):

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto#newc...
sync/protocol/sync.proto:646: optional ClearUserDataMessage clear_user_data = 9;
On 2013/09/06 21:56:44, rlarocque wrote:
> I guess I'm not opposed to this change, but why did it happen?
> 
> Could we use the deprecated option here?

as we discussed offline, this was added back for testing. the client side just
isn't implemented yet.

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto#newc...
sync/protocol/sync.proto:680: // Id of the uploaded crash
On 2013/09/06 21:56:44, rlarocque wrote:
> Add a period?

Done.

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto#newc...
sync/protocol/sync.proto:683: // Time that the crash occurred
On 2013/09/06 21:56:44, rlarocque wrote:
> period?

Done.

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto#newc...
sync/protocol/sync.proto:687: // Proto to be written in its entirety to the
debug info log
On 2013/09/06 21:56:44, rlarocque wrote:
> period?

Done.

https://codereview.chromium.org/23985004/diff/1/sync/protocol/sync.proto#newc...
sync/protocol/sync.proto:689: // Hash of the crashing calltack.
On 2013/09/06 21:56:44, rlarocque wrote:
> typo: calltack.

Done.

[rlarocque, 2013-09-06 22:35:06]

lgtm

[commit-bot: I haz the power, 2013-09-06 22:37:08]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/pvalenzuela@chromium.org/23985004/6001

[pval...(no longer on Chromium), 2013-09-07 00:18:57]

On 2013/09/06 22:37:08, I haz the power (commit-bot) wrote:
> CQ is trying da patch. Follow status at
>
https://chromium-status.appspot.com/cq/pvalenzuela%40chromium.org/23985004/6001

Hmm, this first CQ run is going to fail due to a flaky test.

I'll try and get this in tonight. If not, I'll ping back here so that someone
else can land it next week.

[commit-bot: I haz the power, 2013-09-07 07:20:05]

Change committed as 221910