Cleanup: Remote metadata parameter from ApplyLocalChange

chrome/browser/sync_file_system/local_change_processor.h

Index: chrome/browser/sync_file_system/local_change_processor.h
diff --git a/chrome/browser/sync_file_system/local_change_processor.h b/chrome/browser/sync_file_system/local_change_processor.h
index 2e60a4dcc02469031ea73dc84670c7b7f70eced0..1c637f12f5c4638b929aa8092ce6e26fa9583daa 100644
--- a/chrome/browser/sync_file_system/local_change_processor.h
+++ b/chrome/browser/sync_file_system/local_change_processor.h
@@ -12,7 +12,6 @@ namespace fileapi {
 class FileChange;
 class FileChangeList;
 class FileSystemURL;
-class SyncFileMetadata;
 }
 
 namespace sync_file_system {
@@ -27,15 +26,13 @@ class LocalChangeProcessor {
 
   // This is called to apply the local |change|. If the change type is
   // ADD_OR_UPDATE for a file, |local_file_path| points to a local file
-  // path that contains the latest file image whose file metadata is
-  // |local_file_metadata|.
+  // path that contains the latest file image.
   // When SYNC_STATUS_HAS_CONFLICT is returned the implementation should
   // notify the backing RemoteFileSyncService of the existence of conflict
   // (as the remote service is supposed to maintain a list of conflict files).
   virtual void ApplyLocalChange(
       const fileapi::FileChange& change,
       const FilePath& local_file_path,
-      const fileapi::SyncFileMetadata& local_file_metadata,
       const fileapi::FileSystemURL& url,
       const fileapi::SyncStatusCallback& callback) = 0;