dri-devel Archive on 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: [rerere PATCH] nightly.conf: Update the drm-misc repo
Date: Mon, 26 Feb 2024 12:36:10 +0100	[thread overview]
Message-ID: <20240226113610.46343-2-mripard@kernel.org> (raw)
In-Reply-To: <20240226113610.46343-1-mripard@kernel.org>

drm-misc has moved to gitlab now, so let's update the repo location.

Signed-off-by: Maxime Ripard <mripard@kernel.org>
---
 nightly.conf | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/nightly.conf b/nightly.conf
index c189f2ccad17..0362efd65cf8 100644
--- a/nightly.conf
+++ b/nightly.conf
@@ -37,12 +37,8 @@ https://anongit.freedesktop.org/git/drm/drm-intel
 https://anongit.freedesktop.org/git/drm/drm-intel.git
 "
 drm_tip_repos[drm-misc]="
-ssh://git.freedesktop.org/git/drm/drm-misc
-ssh://git.freedesktop.org/git/drm-misc
-git://anongit.freedesktop.org/drm/drm-misc
-git://anongit.freedesktop.org/drm-misc
-https://anongit.freedesktop.org/git/drm/drm-misc
-https://anongit.freedesktop.org/git/drm/drm-misc.git
+https://gitlab.freedesktop.org/drm/misc/kernel.git
+ssh://git@gitlab.freedesktop.org/drm/misc/kernel.git
 "
 drm_tip_repos[drm]="
 ssh://git.freedesktop.org/git/drm/drm
-- 
2.43.2


  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 ` [dim PATCH] dim: drm-misc: Membership requests now go through Gitlab Maxime Ripard
2024-02-26 11:36   ` Maxime Ripard [this message]
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-2-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox