Thanks Mark.
I tried to search for the specific revision like this:
http://trac.webkit.org/browser?rev=32664
Is this a correct way to search for it?
What branch should I keep an eye on if I want to see if it makes it
into the next version of Safari?
14 nov 2008 kl. 10.11 skrev Mark Rowe:
On Nov 14, 2008, at 12:42 AM, Johan Lund wrote:
I am staring at this bug:
https://bugs.webkit.org/show_bug.cgi?id=7138
which I was really hoping that it would make it into the next
Safari version.
It says version: 420+ in the bug.
That version number is the version that the bug was filed against,
not the version it is fixed in.
Safari 3.2 was released recently and it says it has version
(5525.26.12); way past 420+ in my opinion.
But the bug is not fixed in Safari 3.2.
Correct, the bug is not fixed in Safari 3.2.
Can someone please educate me on how these version numbers actually
work and how I can find out if a bug is supposed to have made it
into Safari...
The version number field of the bug report indicates the version
number that the originator observed the bug in. The SVN revision
number (eg, r32664) given in the comments indicates which revision
of the WebKit trunk contains the fix. There's no particularly easy
way to determine whether or not a bug was fixed in a given release
of Safari. If you're patient, you can look through the Subversion
repository and see which changes were made on the branches that a
given release was made from.
- Mark
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
