Add RemoteChangeProcessor::ClearLocalChanges

chrome/browser/sync_file_system/remote_change_processor.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CHROME_BROWSER_SYNC_FILE_SYSTEM_REMOTE_CHANGE_PROCESSOR_H_
 #define CHROME_BROWSER_SYNC_FILE_SYSTEM_REMOTE_CHANGE_PROCESSOR_H_
 
 #include "base/basictypes.h"
 #include "base/callback_forward.h"
 #include "webkit/fileapi/syncable/sync_callbacks.h"
@@ skipping 43 matching lines @@
   // to a temporary file which has the data downloaded from the server).
   // This may fail with an error but should NOT result in a conflict
   // (as we must have checked the change status in PrepareRemoteSync and
   // have disabled any further writing).
   virtual void ApplyRemoteChange(
       const fileapi::FileChange& change,
       const FilePath& local_path,
       const fileapi::FileSystemURL& url,
       const fileapi::SyncStatusCallback& callback) = 0;
 
+  // Clears all local changes. This should be called when the remote sync
+  // service reconciled or processed the existing local changes while
+  // processing a remote change.
+  virtual void ClearLocalChanges(
+      const fileapi::FileSystemURL& url,
+      const base::Closure& completion_callback) = 0;
+
   // Records a fake local change so that the change will be processed in the
   // next local sync.
   // This is called when the remote side wants to trigger a local sync
   // to propagate the local change to the remote change (e.g. to
   // resolve a conflict by uploading the local file).
   virtual void RecordFakeLocalChange(
       const fileapi::FileSystemURL& url,
       const fileapi::FileChange& change,
       const fileapi::SyncStatusCallback& callback) = 0;
 
  private:
   DISALLOW_COPY_AND_ASSIGN(RemoteChangeProcessor);
 };
 
 }  // namespace sync_file_system
 
 #endif  // CHROME_BROWSER_SYNC_FILE_SYSTEM_REMOTE_CHANGE_PROCESSOR_H_