Add a datatype for supervised user whitelists.

sync/protocol/managed_user_whitelist_specifics.proto

Index: sync/protocol/managed_user_whitelist_specifics.proto
diff --git a/sync/protocol/managed_user_whitelist_specifics.proto b/sync/protocol/managed_user_whitelist_specifics.proto
new file mode 100644
index 0000000000000000000000000000000000000000..b94cf6a1d248f5c8bc697b75421d61713a7351f1
--- /dev/null
+++ b/sync/protocol/managed_user_whitelist_specifics.proto
@@ -0,0 +1,23 @@
+// Copyright (c) 2014 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.
+//
+// Sync protocol datatype extension for supervised user whitelists.
+
+// Update proto_value_conversions{.h,.cc,_unittest.cc} if you change
+// any fields in this file.
+
+syntax = "proto2";
+
+option optimize_for = LITE_RUNTIME;
+option retain_unknown_fields = true;
+
+package sync_pb;
+
+import "extension_specifics.proto";
+
+// Properties of supervised user whitelist sync objects.
+message ManagedUserWhitelistSpecifics {
+  // Extension information.
+  optional ExtensionSpecifics extension = 1;

[Nicolas Zea, 2014/12/15 21:47:53]

Do you really need the full extension specifics? Or is the CRX URL enough?

[Bernhard Bauer, 2014/12/15 22:36:42]

Hmm... I really only need the extension ID and the name. Originally I was
thinking to use a full ExtensionSpecifics so I could pass it straight to the
ExtensionSyncService on desktop, but we've since basically decided to use the
Component Updater for whitelists on desktop as well, so it wouldn't be
necessary. It would make switching back to extensions more difficult, but I
think I'm okay with that. Soo... done! :)

+}