Re: drm-misc migration to Gitlab server

[Helen Koike <helen.koike@collabora.com>]

On 29/04/2024 14:56, Jani Nikula wrote:
> On Mon, 29 Apr 2024, Helen Koike <helen.koike@collabora.com> wrote:
>> On 01/04/2024 13:49, Tvrtko Ursulin wrote:
>>> No issues accessing the repo just a slight confusion and how to handle
>>> the workflow. More specifically, if I have a patch which wants to be
>>> merged to drm-misc-next, is the mailing list based worklflow still the
>>> way to go, or I should create a merge request, or I should apply for
>>> commit access via some new method other than adding permissions to my
>>> legacy fdo ssh account?
>>
>> I have this same question, I thought we would keep the workflow with dim
>> tool, but after I pointed drm-misc remote to gitlab, dim is not happy.
>>
>> If I don't point drm-misc to gitlab, dim say it is outdated (but I'm
>> using the last top of the tree of maintainer-tools).
>>
>> So I was wondering if dim requires changes or if the workflow changed.
> 
> The workflow has not changed, only the location of the repo.

Thanks for confirming.

> 
> I'm afraid there's insufficient info here to say what exactly is going
> on though.

I re-executed dim setup and it seems to be working now.

Thanks.
Helen

> 
> BR,
> Jani.
> 
>