All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@kernel.org>
To: dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	David Airlie <airlied@gmail.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Maxime Ripard <mripard@kernel.org>,
	Daniel Stone <daniels@collabora.com>
Subject: [dim PATCH] dim: drm-misc: Membership requests now go through Gitlab
Date: Mon, 26 Feb 2024 12:36:09 +0100	[thread overview]
Message-ID: <20240226113610.46343-1-mripard@kernel.org> (raw)
In-Reply-To: <gnthy5o42kiyj63d2bkkxsc5krzf3wrwt23chh2kthkmlyjwbg@ybynvjvqdka7>

Now that drm-misc has switched to Gitlab, we don't need to make
newcomers create a legacy SSH account. Gitlab supports access requests,
so let's just use them.

Signed-off-by: Maxime Ripard <mripard@kernel.org>
---
 commit-access.rst | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/commit-access.rst b/commit-access.rst
index 539a7906e52a..3b6c1a19aae2 100644
--- a/commit-access.rst
+++ b/commit-access.rst
@@ -31,9 +31,10 @@ below criteria:
 - Agrees to use their commit rights in accordance with the documented merge
   criteria, tools, processes, and :ref:`code-of-conduct`.
 
-Apply for an account (and any other account change requests) through
+You can apply for developpers right by requesting access to the `drm/misc`
+subgroup on GitLab
 
-https://www.freedesktop.org/wiki/AccountRequests/
+https://gitlab.freedesktop.org/drm/misc
 
 and please ping the maintainers if your request is stuck.
 
-- 
2.43.2


  parent reply	other threads:[~2024-02-26 11:36 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 ` Maxime Ripard [this message]
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=20240226113610.46343-1-mripard@kernel.org \
    --to=mripard@kernel.org \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@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.