-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Romanick wrote:
Brian Paul wrote:
I think we could get by with a shorter beta period. There's a few
more things that would be nice to do for 7.8 which I doubt I'd get to
before the 26th:
Part of the reason for the long lead time is to
On Fri, 2010-02-19 at 14:05 -0800, Corbin Simpson wrote:
On Fri, Feb 19, 2010 at 11:14 AM, Brian Paul bri...@vmware.com wrote:
Guillem Jover wrote:
Hi!
[ CCing Daniel Borca who used to work on 3dfx support in Mesa and
libglide, not sure though if he is around or interested anymore. ]
On Thu, Feb 18, 2010 at 7:25 PM, Brian Paul bri...@vmware.com wrote:
Ian Romanick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Romanick wrote:
All,
It's time again to plan what version or versions of Mesa we want to
release in Q1 (end of March). It seems like 7.7.1 is a
On Thu, Feb 18, 2010 at 9:50 PM, Chia-I Wu olva...@gmail.com wrote:
On Fri, Feb 19, 2010 at 8:25 AM, Brian Paul bri...@vmware.com wrote:
Assuming this plan still works for people, I'll make the mesa_7_8_branch
on Friday, February 26th.
I think we could get by with a shorter beta period.
2010/2/19 Brian Paul brian.e.p...@gmail.com:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
I applied the patches from Kenneth Graunke on the list for this. Can
we drop _mesa_malloc(), _mesa_calloc() and _mesa_free() and
_mesa_bzero() too?
I've remove _mesa_bzero() just now, plus some
Hi!
[ CCing Daniel Borca who used to work on 3dfx support in Mesa and
libglide, not sure though if he is around or interested anymore. ]
On Thu, 2010-02-18 at 17:25:02 -0700, Brian Paul wrote:
3. I'm tempted to remove some old Mesa drivers such as glide, tdfx,
allegro, ggi, dri/mga,
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
2010/2/19 Brian Paul brian.e.p...@gmail.com:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
I applied the patches from Kenneth Graunke on the list for this. Can
we drop _mesa_malloc(), _mesa_calloc() and _mesa_free() and
_mesa_bzero() too?
On Fri, Feb 19, 2010 at 10:59 AM, José Fonseca jfons...@vmware.com wrote:
On Fri, 2010-02-19 at 09:42 -0800, Kristian Høgsberg wrote:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
2010/2/19 Brian Paul brian.e.p...@gmail.com:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
I applied the
On Fri, 2010-02-19 at 09:42 -0800, Kristian Høgsberg wrote:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
2010/2/19 Brian Paul brian.e.p...@gmail.com:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
I applied the patches from Kenneth Graunke on the list for this. Can
we drop
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
2010/2/19 Brian Paul brian.e.p...@gmail.com:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
I applied the patches from Kenneth Graunke on the list for this. Can
we drop _mesa_malloc(),
2010/2/19 Brian Paul brian.e.p...@gmail.com:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
2010/2/19 Brian Paul brian.e.p...@gmail.com:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
I applied the patches from Kenneth Graunke on the list for
On Fri, 2010-02-19 at 10:23 -0800, Kristian Høgsberg wrote:
2010/2/19 Brian Paul brian.e.p...@gmail.com:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
2010/2/19 Kristian Høgsberg k...@bitplanet.net:
2010/2/19 Brian Paul brian.e.p...@gmail.com:
2010/2/19 Kristian Høgsberg
Guillem Jover wrote:
Hi!
[ CCing Daniel Borca who used to work on 3dfx support in Mesa and
libglide, not sure though if he is around or interested anymore. ]
On Thu, 2010-02-18 at 17:25:02 -0700, Brian Paul wrote:
3. I'm tempted to remove some old Mesa drivers such as glide, tdfx,
On Fri, Feb 19, 2010 at 11:14 AM, Brian Paul bri...@vmware.com wrote:
Guillem Jover wrote:
Hi!
[ CCing Daniel Borca who used to work on 3dfx support in Mesa and
libglide, not sure though if he is around or interested anymore. ]
On Thu, 2010-02-18 at 17:25:02 -0700, Brian Paul wrote:
3.
tom fogal wrote:
Ian Romanick i...@freedesktop.org writes:
Since we're not using CVS, would it be possible to start naming the
release branches with just the release version? Likewise for release
tags? Specifically, I'm proposing to use 7.8 for this next branch
and 7.8.0 for the release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
It's time again to plan what version or versions of Mesa we want to
release in Q1 (end of March). It seems like 7.7.1 is a no-brainer. Do
we also want to release Mesa 7.8? I haven't been keeping track of
master, so I don't know what its state
Ian Romanick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
It's time again to plan what version or versions of Mesa we want to
release in Q1 (end of March). It seems like 7.7.1 is a no-brainer. Do
we also want to release Mesa 7.8? I haven't been keeping track of
master,
Sometime over the next day I will update the docs and flesh out the gallium
info. R300g should be marked as testing; it passes roughly as much piglit as
softpipe.
I would only recommend blocking 7.8 to get those gallium docs filled out;
otherwise, no complaints here.
Posting from a mobile,
On Thu, Jan 14, 2010 at 2:52 AM, Ian Romanick i...@freedesktop.org wrote:
-BEGIN PGP SIGNED MESSAGE-
It's time again to plan what version or versions of Mesa we want to
release in Q1 (end of March). It seems like 7.7.1 is a no-brainer. Do
we also want to release Mesa 7.8? I haven't
19 matches
Mail list logo
