Drop remote non-delete directory change if we already know there's a folder
commit4e347a4e8962f589db74b4368e0015863dd6c6bb
authorkinuko@chromium.org <kinuko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 18 Sep 2013 09:07:18 +0000 (18 09:07 +0000)
committerkinuko@chromium.org <kinuko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 18 Sep 2013 09:07:18 +0000 (18 09:07 +0000)
tree8ec2edbfce2c366bddb68593d9ceb288f9a2aae1
parent3a231c5efabce1e38e2d3425a0735a1ebb9619ae
Drop remote non-delete directory change if we already know there's a folder

Without this change, creating a locatl directory triggers two sync events:
1. local sync to create the folder on remote (this is ok), and
2. remote sync (this is not necessary)

BUG=none
TEST=manual

Review URL: https://chromiumcodereview.appspot.com/23567039

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223827 0039d316-1c4b-4281-b951-d872f2087c98
chrome/browser/sync_file_system/drive_backend_v1/drive_file_sync_service.cc