Our goal is to send out such an annoucement once we have it compiling on
Windows.  I'm hopeful that will be very soon.  At that point, it would be a
very good idea for Mac and Linux folks to jump in and find out what they
need to do to ensure that the merge branch doesn't break them :-)
-Darin


On Thu, Oct 23, 2008 at 11:02 AM, Evan Martin <[EMAIL PROTECTED]> wrote:

>
> When you have things looking mostly-ok (e.g. stuff links on Windows),
> can you send out a "will land again soon" warning so we can
> double-check it doesn't break the ports?
>
> On Wed, Oct 22, 2008 at 7:47 PM, Darin Fisher <[EMAIL PROTECTED]> wrote:
> > FYI, we have started the next webkit merge.  This will take us from
> WebKit
> > r36102 to r37604.
> > If you make any changes to third_party/WebKit, please prepare an
> additional
> > CL to port your change to the merge branch.  Your changes will be lost if
> > you do not do this!  The merge branch is located here:
> >
> http://src.chromium.org/viewvc/chrome/branches/chrome_webkit_merge_branch/
> > Also, if you make any changes to third_party/WebKit, please send those
> > changes upstream to the WebKit project.  Ideally you should get your
> change
> > accepted upstream before attempting to apply it to our copy in
> > third_party/WebKit.  This is important because we cannot afford to
> further
> > fork WebCore!
> > If you need help regarding the next merge, please ask me, dglazkov, ojan
> or
> > mbelshe :-)
> > Cheers,
> > -Darin
> > >
> >
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to chromium-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to