On 2/10/2011 5:58 PM, ext Ademar Reis wrote:
In this case it did land on trunk and, in a different form, on 2.1.x.
But it was not fixed in 2.0 (where it sould be before getting to
qt-4.7/src/3rdparty/webkit/) nor in 2.1.
Just to make it clear: there should be no patches added on
qt-4.7/src/3rdparty/webkit/. We should have commits on our qtwebkit
repositories and only imports/syncs on the qt repositories (commits
like "Update QtWebKit to<SHA1>"). Unfortunately there's no mechanism
in place to prevent that, AFAIK.
It always has been a problem since people don't know how or don't want
to deal with WebKit trunk's committing policy.
Once Qt's modularization sees the day, QtWebKit will stay out of
src/3rdparty, and this problem will merely be a sad thought of the past. :)
Jocelyn
_______________________________________________
webkit-qt mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
