From: Maxime Ripard <mripard@kernel.org>
To: 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: Tue, 20 Feb 2024 10:04:59 +0100 [thread overview]
Message-ID: <akb3fluuli75vh5due5ll7t5igg7oo5vqwkal645hkjkhyqz6w@qu62f5l6joy6> (raw)
In-Reply-To: <gnthy5o42kiyj63d2bkkxsc5krzf3wrwt23chh2kthkmlyjwbg@ybynvjvqdka7>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> Hi,
>
> As you might have noticed in your mails, Daniel Stone and I have been
> working on adding all the drm-misc maintainers and committers to Gitlab.
>
> The current repository was still in the cgit instance and was creating
> an unnecessary burden on the admins.
>
> For example, any new user had to create an issue and go through Daniel
> to create an cgit account, even though that user already needed to have
> a gitlab account to create the issue in the first place. Adding an SSH
> key was a similar story. By moving to Gitlab, we'll remove most of that
> burden.
>
> This will be mostly transparent to current committers and users: we'll
> still use dim, in the exact same way, the only change will be the URL of
> the repo. This will also be transparent to linux-next, since the
> linux-next branch lives in its own repo and is pushed by dim when
> pushing a branch.
Actually, I double-checked and linux-next pulls our branches directly,
so once the transition is over we'll have to notify them too.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-02-20 9:05 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 [this message]
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
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=akb3fluuli75vh5due5ll7t5igg7oo5vqwkal645hkjkhyqz6w@qu62f5l6joy6 \
--to=mripard@kernel.org \
--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=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.