[webkit-dev] Merging the iOS port to svn.webkit.org (Re: WebCore and interlocking threads)
abarth at webkit.org
Sat Feb 9 10:11:56 PST 2013
On Fri, Feb 8, 2013 at 8:19 PM, Maciej Stachowiak <mjs at apple.com> wrote:
> On Feb 8, 2013, at 2:33 PM, Darin Fisher <darin at chromium.org> wrote:
> I would recommend minimizing the re-architecture of WebCore as you are in
> the early stages of upstreaming. It seems like you already have a working
> port that you could simply upstream. You could then work with others in
> the community to introduce new concepts to WebCore with the full disclosure
> of code as an aide to the process. Another option might be to open source
> the entire thing as a branch somewhere.
> After the initial upstreaming or sharing of code is complete, you could
> then catalog all of the warts. The fact that isMainThread returns true
> when called on more than one thread would be one such wart. I can imagine
> a meta bug tracking all of these warts. This would make it a lot easier
> for others to understand the overall change in direction needed for WebKit
> to properly support the iOS port.
> That's approximately what we're planning to do. We are upstreaming
> incrementally, starting with simple pieces, and documenting issues. The bug
> that sparked this thread was a relatively change to isMainThread(), plus a
> function rename, and we are no longer asking for the function rename. It
> will likely be a dozen line patch touching a single mac/ios-specific file.
> We'd really like to fully upstream the simpler components like WTF (where
> the changes are all simple and targeted) even if we can't as easily do
> WebCore (where there may be more complex and controversial diffs).
More information about the webkit-dev