> On Oct 22, 2022, at 12:11 PM, Caitlin Potter wrote:
>
> Would it make sense to, rather than referring to downstream browsers, have a
> canonical WebKit version number that could be exposed in about:version or
> something? A friendly semver-ish thing + short git hash could be a lot more
> use
Would it make sense to, rather than referring to downstream browsers, have a
canonical WebKit version number that could be exposed in about:version or
something? A friendly semver-ish thing + short git hash could be a lot more
useful for doing things like bisecting.
I think part of the reason t
Indeed, I'd love it those didn't exist.
(I always imagined them to be exclusively intended for bug reports originating
from non-contributors, but I'm not even certain how much they've been used in
that scenario.)
From: Michael Catanzaro via webkit-dev
Sent: Satur
On Sat, Oct 22 2022 at 07:31:06 AM -0700, Darin Adler via webkit-dev
wrote:
Can we just get rid of all this?
That would be nice. These labels are not useful for pull requests.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.we
Hi folks.
I understand it can be super critical to understand what version someone was
testing when reporting a WebKit bug. But I, at least, haven’t found the version
field at bugs.webkit.org useful in the 20+ years I have been working on this
project.
Now we have that same noise in GitHub. Al
5 matches
Mail list logo
