This looks good.  Thanks, Mads.

Mark

Mads wrote:
> I am committing the following in the v8 repository now.  I'll push
> this to chromium ASAP to hopefully solve this issue.  Thanks for
> bringing it to my attention.
>
> -- Mads
>
> a...@redex:~/v8/v8$ svn diff
>
> Property changes on: tools/gyp
> ___________________________________________________________________
> Added: svn:ignore
>   + d8_js2c.vcproj
> js2c.vcproj
> mksnapshot.vcproj
> v8.sln
> v8.vcproj
> v8_base.vcproj
> v8_nosnapshot.vcproj
> v8_shell.vcproj
> SConstruct
> d8_js2c.scons
> js2c.scons
> mksnapshot.scons
> v8.scons
> v8_base.scons
> v8_main.scons
> v8_nosnapshot.scons
> v8_shell.scons
> v8.xcodeproj
>
>
> On Thu, Apr 30, 2009 at 9:25 AM, Bradley Nelson <[email protected]> wrote:
>> So with generated sln and vcprojs, it affects everyone who syncs, so
>> everwhere else svn:ignore gets used.
>>
>> To do this:
>> svn propedit svn:ignore dircontainingfilestoignore
>> Then list the vcprojs and slns one per line.
>> The properties are actually on the directory not the file. Then the
>> directory is treated as modified for the current change. One gotcha, gcl
>> doesn't understand props, so it won't show up in reidfeld. Also gcl won't
>> commit a cl with only props changes, so if you only change props you'll have
>> to use svn commit instead.
>>
>> -bradn
>>
>> On Apr 29, 2009 11:05 PM, "Mads Sig Ager" <[email protected]> wrote:
>>
>> How is this normally handled?  So far, we have not asked svn to ignore
>> anything in the v8 repository.  We leave it up to the individual
>> developer to manage his settings for that.  For the other gyp
>> generated files, is this handled by setting something in the chromium
>> repository, or is it handled by the tr servers?
>>
>> Thanks,    -- Mads
>>
>> On Wed, Apr 29, 2009 at 6:48 PM, <[email protected]> wrote: > Looks like you
>> didn't set svn:ignore...
>

--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to