Chromium Code Reviews| Index: sync/protocol/sync_enums.proto |
| diff --git a/sync/protocol/sync_enums.proto b/sync/protocol/sync_enums.proto |
| index 9305c677384a481f73009390f5936eee3f9c52ad..60c2e55899243de45f6baf041754952d83b175df 100644 |
| --- a/sync/protocol/sync_enums.proto |
| +++ b/sync/protocol/sync_enums.proto |
| @@ -113,7 +113,9 @@ message SyncEnums { |
| STOP_AND_RESTART_SYNC = 3; // Stop sync and set up sync again. |
| DISABLE_SYNC_ON_CLIENT = 4; // Wipe the client of all sync data and |
| // stop syncing. |
| - UNKNOWN_ACTION = 5; // This is the default. |
| + DISABLE_SYNC_AND_ROLLBACK = 5; // Wipe out sync data, stop syncing and |
| + // roll back local data to pre-sync state. |
| + UNKNOWN_ACTION = 6; // This is the default. |
|
Nicolas Zea
2014/04/15 23:08:31
it's a bit concerning that we're modifying the val
maniscalco
2014/04/15 23:16:26
I was wondering the same thing. Is Action ever se
haitaol1
2014/04/15 23:44:03
I think it's by design that UNKNOWN_ACTION is put
maniscalco
2014/04/16 00:09:20
To make things "obviously safe" I suggest leaving
|
| } |
| enum DeviceType { |