For MathML we have a master bug 3251 that we've been making depend
on every new patch for MathML. That is a very nice in that as new patches
are added and committed, you can get notifications of the changes
in status.
We also have the MathML component that all bugs should be associated
with. As
Independently of the other long thread, I'd like to express my love of
the commit queue. It is actually quite a nice feature for someone like
myself who is off in a corner.
I don't want commit access. I'd rather my changes go through some
process like the commit queue to ensure that it doesn't
On Jul 8, 2010, at 11:04 AM, Kevin Ollivier kev...@theolliviers.com wrote:
I'm working on making the CPP DOM bindings accessible to the wx port, and
while I've got the whole thing building, one thing I have yet to sort out is
how to add building of the CPP DOM bindings to the build system.
On Jul 9, 2010, at 6:23 AM, Alex Milowski wrote:
For MathML we have a master bug 3251 that we've been making depend
on every new patch for MathML. That is a very nice in that as new patches
are added and committed, you can get notifications of the changes
in status.
If all you're concerned
On Jul 9, 2010, at 3:38 AM, Alex Milowski wrote:
Being able to go around the commit queue means you can cheat. That
seems like something that should be reserved for more severe problems
where we know the process used by the commit queue will fail.
That is not how I see it at all. And calling
On Fri, Jul 9, 2010 at 3:39 PM, Timothy Hatcher timo...@apple.com wrote:
On Jul 9, 2010, at 3:38 AM, Alex Milowski wrote:
Being able to go around the commit queue means you can cheat. That
seems like something that should be reserved for more severe problems
where we know the process used by
On Fri, Jul 9, 2010 at 7:39 AM, Timothy Hatcher timo...@apple.com wrote:
Some of the glaring reasons I don't use the commit queue have been resolved
(svn blame mainly), but the fact that there is no control over when the path
lands is my chief reason.
I agree. When my patch has a potential
I filled a bug and submitted a patch with fonts and license only:
https://bugs.webkit.org/show_bug.cgi?id=41961
Does anyone could tell if this license is compatible with the WebKit one?
François Sausset
Le 7 juil. 2010 à 21:25, Dan Bernstein a écrit :
On Jul 7, 2010, at 11:17 AM, Sausset
On Jul 9, 2010, at 7:34 AM, Adam Roben wrote:
I think an important question to ask is, When will you move the master bug
to Resolved/Fixed? This is basically another way of saying, What task(s)
does the master bug represent? Once you know that answer, the answers to
your other questions
/Volumes/Data/WebKit-BuildSlave/snowleopard-intel-release/build/WebCore/config.h:212:
fatal error: error writing to -: Broken pipe
compilation terminated.
i686-apple-darwin10-gcc-4.2.1: Internal error: Segmentation fault (program as)
Please submit a full bug report.
See
No theories. But another data point; Tiger started doing the same a few
revisions earlier:
/Volumes/Data/WebKit-BuildSlave/tiger-intel-release/build/WebKit/mac/WebView/WebView.mm:
In function 'void -[WebView(WebPrivate)
_commonInitializationWithFrameName:groupName:usesDocumentViews:](WebView*,
This has landed. Squashing is now the default behavior. --git-commit/-g
operates on the commit(s) listed as a single commit. --git-commit=HEAD..
operates on the working copy.
Ojan
On Mon, May 24, 2010 at 5:10 PM, Ojan Vafai o...@chromium.org wrote:
I posted a patch to
On Jul 9, 2010, at 7:34 AM, Adam Roben aro...@apple.com wrote:
On Jul 9, 2010, at 6:23 AM, Alex Milowski wrote:
Should we keep the master bug?
Should we use it only for our implementation efforts and not
make it depend on every random bug filed for the MathML
component?
I think an
On Fri, Jul 9, 2010 at 6:19 PM, David Kilzer ddkil...@webkit.org wrote:
On Jul 9, 2010, at 7:34 AM, Adam Roben aro...@apple.com wrote:
On Jul 9, 2010, at 6:23 AM, Alex Milowski wrote:
Should we keep the master bug?
Should we use it only for our implementation efforts and not
make it
14 matches
Mail list logo
