Multi-profile flag cleanup

chrome/common/chrome_switches.cc

Index: chrome/common/chrome_switches.cc
diff --git a/chrome/common/chrome_switches.cc b/chrome/common/chrome_switches.cc
index 13aa5b9bc0b69edfbbb4599a7326833032392d67..0b17d4c5bd4d7f7b87e81294da3af402bc754193 100644
--- a/chrome/common/chrome_switches.cc
+++ b/chrome/common/chrome_switches.cc
@@ -888,7 +888,9 @@ const char kMessageLoopHistogrammer[]       = "message-loop-histogrammer";
 const char kMetricsRecordingOnly[]          = "metrics-recording-only";
 
 // Enables multiprofile Chrome.
-const char kMultiProfiles[]                 = "multi-profiles";
+// TODO(zelidrag): Remove this one completely in M-38+ once most profiles

[Nikita (slow), 2014/05/19 14:27:15]

What about users that will update from pre-M-37 profiles and will miss that
migration process? I assume non-existing flags should just get ignored somehow
and don't require Chrome browser process restart.

[zel, 2014/05/19 18:06:27]

Actually, it seems that we don't have to do this type of filtering at all since
FlagsState::ConvertFlagsToSwitches()/GetSanitizedEnabledFlagsForCurrentPlatform()
takes care for this.

Removed.

+// that got infected with it through about://flags are cleaned.
+const char kMultiProfilesObsolete[]         = "multi-profiles";
 
 // Sets the base logging level for the net log. Log 0 logs the most data.
 // Intended primarily for use with --log-net-log.