Add support for the quick-enable-cf command to the installer. This encompase...

chrome/installer/setup/install_worker.h

Index: chrome/installer/setup/install_worker.h
===================================================================
--- chrome/installer/setup/install_worker.h	(revision 76372)
+++ chrome/installer/setup/install_worker.h	(working copy)
@@ -136,6 +136,15 @@
 // Refreshes the elevation policy on platforms where it is supported.
 void RefreshElevationPolicy();
 
+// Add work items to add or remove the "quick-enable-cf" to the multi-installer
+// binaries' version key.   |setup_path| and |new_version| are required when

[robertshield, 2011/03/02 14:58:57]

Three spaces after a period? That's a lot of space.

[grt (UTC plus 2), 2011/03/02 19:48:28]

Inflation, don't you know.

+// processing product installation; they may be NULL when uninstalling.

[erikwright (departed), 2011/03/02 15:18:16]

'may' or 'must'?

After reviewing the implementation, I understand that this function decides,
based on the installer and installation state, whether to add, remove, or leave
unmodified the product commands. I think the comment here could better reflect
that fact.

Even when reading the call sites, the name is a bit confusing. Ideally, the name
would be something that said
"AddWorkItemsToAddOrRemoveQuickEnableProductCommand" but that's a bit long :(

[grt (UTC plus 2), 2011/03/02 19:48:28]

Nothing will break if they aren't NULL on uninstall, so I wouldn't say must. 
I've updated the comment to make it clear that they're not used on uninstall.
Done.

+void AddQuickEnableWorkItems(const InstallerState& installer_state,
+                             const InstallationState& machine_state,
+                             const FilePath* setup_path,
+                             const Version* new_version,
+                             WorkItemList* work_item_list);
+
 }  // namespace installer
 
 #endif  // CHROME_INSTALLER_SETUP_INSTALL_WORKER_H_