From: Tvrtko Ursulin <tursulin@ursulin.net>
To: 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, 1 Apr 2024 17:49:48 +0100 [thread overview]
Message-ID: <2ddb4f5e-504e-4ce3-95d2-179dc7e6bf7b@ursulin.net> (raw)
In-Reply-To: <20240312-bizarre-rational-sawfish-ccee0a@houat>
On 12/03/2024 13:56, Maxime Ripard wrote:
> Hi,
>
> On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
>> ## Changing the default location repo
>>
>> Dim gets its repos list in the drm-rerere nightly.conf file. We will
>> need to change that file to match the gitlab repo, and drop the old cgit
>> URLs to avoid people pushing to the wrong place once the transition is
>> made.
>>
>> I guess the next merge window is a good time to do so, it's usually a
>> quiet time for us and a small disruption would be easier to handle. I'll
>> be off-duty during that time too, so I'll have time to handle any
>> complication.
>>
>> ## Updating the documentation
>>
>> The documentation currently mentions the old process to request a
>> drm-misc access. It will all go through Gitlab now, so it will change a
>> few things. We will also need to update and move the issue template to
>> the new repo to maintain consistency.
>>
>> I would expect the transition (if everything goes smoothly) to occur in
>> the merge-window time frame (11/03 -> 24/03).
>
> The transition just happened. The main drm-misc repo is now on gitlab,
> with the old cgit repo being setup as a mirror.
>
> If there's any issue accessing that gitlab repo, please let me know.
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?
Regards,
Tvrtko
next prev parent reply other threads:[~2024-04-01 16:49 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 [this message]
2024-04-29 17:06 ` Helen Koike
2024-04-29 17:56 ` Jani Nikula
2024-04-29 18:29 ` Helen Koike
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=2ddb4f5e-504e-4ce3-95d2-179dc7e6bf7b@ursulin.net \
--to=tursulin@ursulin.net \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--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.