Re: [Piglit] [Mesa-dev] GitLab migration of Piglit

2019-02-20 Thread Den
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

Re: [Piglit] [Mesa-dev] GitLab migration of Piglit

2018-06-05 Thread Emil Velikov
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

Re: [Piglit] [Mesa-dev] GitLab migration of Piglit

2018-06-05 Thread Eric Engestrom
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

Re: [Piglit] [Mesa-dev] GitLab migration of Piglit

2018-06-04 Thread Marek Olšák
I would say it's a sub-project of Mesa. Marek On Mon, Jun 4, 2018 at 11:48 AM, Jason Ekstrand wrote: > 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