From: Helen Koike <helen.koike@collabora.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Stone <daniels@collabora.com>
Subject: Re: drm-misc migration to Gitlab server
Date: Mon, 29 Apr 2024 15:29:23 -0300 [thread overview]
Message-ID: <5ec8add9-7cd1-46dc-be6d-2e2d9808867c@collabora.com> (raw)
In-Reply-To: <87sez42gtg.fsf@intel.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.
>
>
prev parent reply other threads:[~2024-04-29 18:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 8:49 drm-misc migration to Gitlab server Maxime Ripard
2024-02-20 9:04 ` Maxime Ripard
2024-02-20 11:25 ` Daniel Stone
2024-02-20 22:46 ` Stephen Rothwell
2024-02-21 0:22 ` Daniel Stone
2024-02-26 14:50 ` Daniel Vetter
2024-02-26 21:35 ` Stephen Rothwell
2024-02-28 16:33 ` Daniel Vetter
2024-02-28 21:56 ` Stephen Rothwell
2024-03-14 8:39 ` Maxime Ripard
2024-03-14 10:00 ` Stephen Rothwell
2024-02-26 11:33 ` Jani Nikula
2024-02-26 11:41 ` Maxime Ripard
2024-02-26 11:57 ` Jani Nikula
2024-02-26 12:00 ` Daniel Stone
2024-02-26 12:03 ` Jani Nikula
2024-02-26 12:09 ` Daniel Stone
2024-02-26 13:14 ` Maxime Ripard
2024-02-26 11:36 ` [dim PATCH] dim: drm-misc: Membership requests now go through Gitlab Maxime Ripard
2024-02-26 11:36 ` [rerere PATCH] nightly.conf: Update the drm-misc repo Maxime Ripard
2024-02-28 14:18 ` drm-misc migration to Gitlab server Daniel Vetter
2024-03-01 16:11 ` Maxime Ripard
2024-03-06 15:29 ` [rerere PATCH v2] nightly.conf: Update the drm-misc repo Maxime Ripard
2024-03-06 15:38 ` [PATCH v2 1/2] MAINTAINERS: Update drm-misc.git URL Maxime Ripard
2024-03-06 15:38 ` [PATCH v2 2/2] MAINTAINERS: Update drm-misc web page Maxime Ripard
2024-03-07 14:02 ` Jani Nikula
2024-03-08 9:49 ` Maxime Ripard
2024-03-12 13:56 ` drm-misc migration to Gitlab server Maxime Ripard
2024-04-01 16:49 ` Tvrtko Ursulin
2024-04-29 17:06 ` Helen Koike
2024-04-29 17:56 ` Jani Nikula
2024-04-29 18:29 ` Helen Koike [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ec8add9-7cd1-46dc-be6d-2e2d9808867c@collabora.com \
--to=helen.koike@collabora.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.