Why the ENABLE? Why not BROWSER_SYNC? -Scott
On Wed, Oct 14, 2009 at 12:23 PM, Munjal Doshi <[email protected]> wrote: > I like ENABLE_BROWSER_SYNC too. > > -Munjal > > On Wed, Oct 14, 2009 at 12:17 PM, Tim Steele <[email protected]> wrote: >> >> (chromium-dev-izing thread) >> Are we still a month from having the platforms build? If we aren't do we >> have another way to disable a feature per platform, or just command line >> flags? >> I'm cool with ENABLE_BROWSER_SYNC though. >> >> On Wed, Oct 14, 2009 at 12:13 PM, Nick Carter <[email protected]> wrote: >>> >>> The #define CHROME_PERSONALIZATION is the last remaining vestige of sync >>> obfuscation. We will need a feature define until sync is enabled by default >>> for all builds (mac, linux, chromeos). That's a month or more. >>> In the meantime, CHROME_PERSONALIZATION is an unintuitive name. I >>> propose changing it to ENABLE_BROWSER_SYNC. >>> Any objections or counter-proposals? >>> - nick >>> >>> -- >>> >>> You received this message because you are subscribed to the Google Groups >>> "chrome-sync-dev" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/a/google.com/group/chrome-sync-dev?hl=en. >> >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
