Without objection, I'll move forward with renaming to BROWSER_SYNC.
- nick
On Wed, Oct 14, 2009 at 1:10 PM, Evan Stade wrote:
> I always thought PERSONALIZATION was weird.
>>
>
> I believe that was the point.
>
--~--~-~--~~~---~--~~
Chromium Developers mailing
>
> I always thought PERSONALIZATION was weird.
>
I believe that was the point.
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium
BROWSER_SYNC++ I always thought PERSONALIZATION was weird.
- Mohamed Mansour
On Wed, Oct 14, 2009 at 3:33 PM, Scott Violet wrote:
>
> Why the ENABLE? Why not BROWSER_SYNC?
>
> -Scott
>
> On Wed, Oct 14, 2009 at 12:23 PM, Munjal Doshi
> wrote:
> > I like ENABLE_BROWSER_SYNC too.
> >
> > -Mu
Why the ENABLE? Why not BROWSER_SYNC?
-Scott
On Wed, Oct 14, 2009 at 12:23 PM, Munjal Doshi wrote:
> I like ENABLE_BROWSER_SYNC too.
>
> -Munjal
>
> On Wed, Oct 14, 2009 at 12:17 PM, Tim Steele wrote:
>>
>> (chromium-dev-izing thread)
>> Are we still a month from having the platforms build?
I like ENABLE_BROWSER_SYNC too.
-Munjal
On Wed, Oct 14, 2009 at 12:17 PM, Tim Steele 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 wi
(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 wrote:
> The #define CHROM
