On 04/05/2016 12:30 PM, Jason Ekstrand wrote:
...
> If people step up with code review, I'm hoping that we can merge some
> time this week or next.
>
> --Jason Ekstrand
Woo! The Vulkan code is finally merged!
___
mesa-dev mailing list
mesa-dev@lists.f
Jason Ekstrand writes:
> All,
>
> We are getting very close to being able to merge the Vulkan driver into
> mesa master. I've got around 30 patches on the mailing list that are still
> awaiting review. Once those get merged, the diff between the "vulkan" and
> "master" branches is basically zer
On Thu, Apr 7, 2016 at 4:34 PM, Grazvydas Ignotas wrote:
> Hi,
>
> On Tue, Apr 5, 2016 at 10:30 PM, Jason Ekstrand wrote:
>> I know we don't usually do merges in this project, but
>> the Vulkan driver is big and has a lot of history that we would like to
>> preserve. If you're strongly opposed t
On Thu, Apr 7, 2016 at 4:48 PM, Jason Ekstrand wrote:
>
>
> On Thu, Apr 7, 2016 at 4:34 PM, Grazvydas Ignotas
> wrote:
>
>> Hi,
>>
>> On Tue, Apr 5, 2016 at 10:30 PM, Jason Ekstrand
>> wrote:
>> > I know we don't usually do merges in this project, but
>> > the Vulkan driver is big and has a lot
On Thu, Apr 7, 2016 at 4:34 PM, Grazvydas Ignotas wrote:
> Hi,
>
> On Tue, Apr 5, 2016 at 10:30 PM, Jason Ekstrand
> wrote:
> > I know we don't usually do merges in this project, but
> > the Vulkan driver is big and has a lot of history that we would like to
> > preserve. If you're strongly opp
Hi,
On Tue, Apr 5, 2016 at 10:30 PM, Jason Ekstrand wrote:
> I know we don't usually do merges in this project, but
> the Vulkan driver is big and has a lot of history that we would like to
> preserve. If you're strongly opposed to doing a merge, please speak up now!
I fear issues like the one
Hi Jason,
On 5 April 2016 at 20:30, Jason Ekstrand wrote:
> All,
>
> We are getting very close to being able to merge the Vulkan driver into mesa
> master. I've got around 30 patches on the mailing list that are still
> awaiting review. Once those get merged, the diff between the "vulkan" and
>
