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

[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 contributing to it. Before (again, 
same with mesa) we created mailing threads and after reviewing test was 
pushed to master by somebody with access.
Now mesa got a new possibility for reviewing - merge requests, which 
doesn't exist in piglit. Also, according to Jason's conclusion, anybody 
can request commit access to piglit. But in this case how the review 
process will be done?

Thank you in advance.


On 6/7/18 10:18 AM, Daniel Stone wrote:
> Hi Emil,
>
> On 5 June 2018 at 18:21, Emil Velikov <emil.l.velikov at gmail.com> wrote:
>> On 5 June 2018 at 18:02, Daniel Stone <daniel at fooishbar.org> 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/$foo.
>> I'd image the same approach will be adopted in gitlab?
> Unfortunately not, it provides a single canonical URL rather than
> aliasing. But both old anongit URLs will continue to work.
>
>>>>> llvm.git
>> Empty - nuke?
> Done.
>
>>>>> mesa-test.git
>> Plain copy/paste just like xserver-test. There were no extra
>> branches/patches wrt the usual repos.
>> Nuke?
> Done.
>
>>>>> libwsbm.git
>>>>> linux-agp-compat.git
>>>>> vmwgfx.git
>> Might want to check with the VMware people about these.
>> I'm suspecting that the developers are not keeping a close eye on mesa-dev@
> I'm going to follow up with them separately about vmwgfx.git.
>
> Cheers,
> Daniel
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev