>> > distinguish
>> > On 2012/05/16 07:55:36, Mads Sig Ager wrote:
>> > > Please update the comment as well. :)
>> > Done.
> I'll land this then.
> Landed as r11590.
Thanks!
> Please base your future CLs on svn/bleeding_edge instead of
> svn/trunk :)
Will do. Is there a wiki page somewhere that explains how to send out
patches to v8 when using the v8 directory in a chromium checkout? I just
did `cd v8; gcl change blah; gcl upload blah;`, and chromium seems to pull
from svn/trunk.
On Fri, May 18, 2012 at 3:57 PM, Nico Weber <tha...@chromium.org> wrote:
> Will do. Is there a wiki page somewhere that explains how to send out
> patches to v8 when using the v8 directory in a chromium checkout? I just
> did `cd v8; gcl change blah; gcl upload blah;`, and chromium seems to pull
> from svn/trunk.
There isn't, because that's not supported.
V8 development happens on svn/branches/bleeding_edge; a few times per week
we push a reasonably stable snapshot of that to svn/trunk, and roll that
into Chromium.
So, to contribute to V8 (which you are most welcome to!), you should get a
checkout of bleeding_edge. See http://code.google.com/p/v8/wiki/Source (SVN)
or http://code.google.com/p/v8/wiki/UsingGit (git). These checkouts work
with gcl/git-cl just fine, so you'll get pretty close to your usual
Chromium workflow (biggest difference: there are no try bots for V8).