Given the discussion below, I think we'll make piglit a sub-project of
mesa. Those who need commit access to piglit but not mesa can be
added directly to the piglit project.
Hi list.
Since piglit was also moved to the gitlab, same with mesa, our team is
interested in process workflow for con
Hi Emil,
On 5 June 2018 at 18:21, Emil Velikov wrote:
> On 5 June 2018 at 18:02, Daniel Stone wrote:
drm-gralloc.git
> Empty - please nuke, alongside bugzilla & other infra.
Done.
drm.git
> Out of curiosity - this and others (say igt) projects are accessible
> as mesa/$foo and drm/$f
Hi Dan,
Sharing a couple of small ideas.
On 5 June 2018 at 18:02, Daniel Stone wrote:
>>> drm-gralloc.git
Empty - please nuke, alongside bugzilla & other infra.
>>> drm.git
Out of curiosity - this and others (say igt) projects are accessible
as mesa/$foo and drm/$foo.
I'd image the same approa
On 5 June 2018 at 17:55, Eric Engestrom wrote:
> On Tuesday, 2018-06-05 17:52:17 +0100, Daniel Stone wrote:
>> > I assume that's now mesa, libdrm, piglit, shader-db, crucible, kmscube,
>> > mesa-demos; what about igt? Anything else?
>>
>> We currently have under /git/mesa:
>> clover.git
>> crucibl
On Tuesday, 2018-06-05 17:52:17 +0100, Daniel Stone wrote:
> Hi Eric,
>
> On 5 June 2018 at 17:49, Eric Engestrom wrote:
> > On Tuesday, 2018-06-05 09:11:58 -0700, Jason Ekstrand wrote:
> >> Given the discussion below, I think we'll make piglit a sub-project of
> >> mesa. Those who need commit a
Hi Eric,
On 5 June 2018 at 17:49, Eric Engestrom wrote:
> On Tuesday, 2018-06-05 09:11:58 -0700, Jason Ekstrand wrote:
>> Given the discussion below, I think we'll make piglit a sub-project of
>> mesa. Those who need commit access to piglit but not mesa can be added
>> directly to the piglit pro
On Tuesday, 2018-06-05 09:11:58 -0700, Jason Ekstrand wrote:
> Given the discussion below, I think we'll make piglit a sub-project of
> mesa. Those who need commit access to piglit but not mesa can be added
> directly to the piglit project.
>
> Unless someone objects strongly, I'll plan to migrat
Given the discussion below, I think we'll make piglit a sub-project of
mesa. Those who need commit access to piglit but not mesa can be added
directly to the piglit project.
Unless someone objects strongly, I'll plan to migrate piglit on Thursday
along with all the other mesa repos.
On Mon, Jun
Jason Ekstrand writes:
> All,
>
> Sorry for the mess of GitLab e-mails but there are a lot of questions to
> ask as this process moves forward. Today, we're discussing piglit. I've
> included both the mesa and piglit list in the hopes that people will
> actually see this e-mail.
>
> Honestly, I
