> I was referring mostly to build-webkit ifs, assuming that the #ifdefs
> in the cpp code were still around as well. But it's possible those
> already got removed. :)
I think Eric's question is broader than just #ifdefs. Bugzilla has
some Tiger bugs that we should close if we consider Tiger's sup
I was referring mostly to build-webkit ifs, assuming that the #ifdefs
in the cpp code were still around as well. But it's possible those
already got removed. :)
-eric
On Tue, May 3, 2011 at 11:07 AM, Mark Rowe wrote:
>
> On 2011-05-03, at 10:58, Eric Seidel wrote:
>
>> It looks like Tiger suppo
On 2011-05-03, at 10:58, Eric Seidel wrote:
> It looks like Tiger support in WebKit is slowly being removed. There
> no longer is a libWebKitSystemInterfaceTiger.a in the project, nor is
> there a Tiger buildbot or tiger expectations.
>
> Can we go ahead and kill all the ifdefs too? Or is it t
It looks like Tiger support in WebKit is slowly being removed. There
no longer is a libWebKitSystemInterfaceTiger.a in the project, nor is
there a Tiger buildbot or tiger expectations.
Can we go ahead and kill all the ifdefs too? Or is it too early to
call Tiger dead?
-eric
I discussed this with various folks in IRC and was told that answering
this question is difficult w.r.t. Apple's need for confidentiality
around some topics. Apparently, when folks are able to say something,
they'll let us know.
Adam
On Thu, Oct 21, 2010 at 8:04 AM, Jeremy Orlow wrote:
> Ping?
Ping?
On Mon, Oct 11, 2010 at 9:26 AM, Adam Barth wrote:
> I don't see a Tiger buildbot anymore. Does that mean I'm allowed to
> break the Tiger build? If so, can we rip out all the Tiger-specific
> code?
>
> Adam
> ___
> webkit-dev mailing list
> we
I don't see a Tiger buildbot anymore. Does that mean I'm allowed to
break the Tiger build? If so, can we rip out all the Tiger-specific
code?
Adam
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webk
7 matches
Mail list logo
