Fix handling of undeletion within the syncer.

chrome/browser/sync/engine/post_commit_message_command.cc

Index: chrome/browser/sync/engine/post_commit_message_command.cc
diff --git a/chrome/browser/sync/engine/post_commit_message_command.cc b/chrome/browser/sync/engine/post_commit_message_command.cc
index eea5d0e9f66d745b03bc3e789e11ef345b0033c6..92a4cc443509b0a49ea38e1cb47411ae14f11e54 100644
--- a/chrome/browser/sync/engine/post_commit_message_command.cc
+++ b/chrome/browser/sync/engine/post_commit_message_command.cc
@@ -28,11 +28,11 @@ void PostCommitMessageCommand::ExecuteImpl(sessions::SyncSession* session) {
   if (!dir.good())
     return;
   sessions::StatusController* status = session->status_controller();
-  if (!SyncerProtoUtil::PostClientToServerMessage(
-      status->mutable_commit_message(), &response, session)) {
+  if (!SyncerProtoUtil::PostClientToServerMessage(status->commit_message(),
+          &response, session)) {
     // None of our changes got through.  Clear the SYNCING bit which was
     // set to true during BuildCommitCommand, and which may still be true.
-    // Not to be confused with IS_UNSYNCED.  This bit is used to detect local
+    // Not to be confused with IS_UNSYNCED, this bit is used to detect local
     // changes to items that happen during the server Commit operation.
     status->increment_num_consecutive_errors();
     syncable::WriteTransaction trans(dir, syncable::SYNCER, __FILE__, __LINE__);