dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Stone <daniel@fooishbar.org>,
	Maxime Ripard <mripard@kernel.org>,
	dri-devel@lists.freedesktop.org, 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: Thu, 29 Feb 2024 08:56:28 +1100	[thread overview]
Message-ID: <20240229085628.44b5e53c@canb.auug.org.au> (raw)
In-Reply-To: <Zd9gWOnpPf5XbR-j@phenom.ffwll.local>

[-- Attachment #1: Type: text/plain, Size: 632 bytes --]

Hi Daniel,

On Wed, 28 Feb 2024 17:33:28 +0100 Daniel Vetter <daniel@ffwll.ch> wrote:
>
> > git://git.freedesktop.org/git/drm/drm.git#drm-fixes
> > git://git.freedesktop.org/git/drm/drm.git#drm-next  
> 
> To test out the process we've moved drm.git first. It's now here:
> 
> https://gitlab.freedesktop.org/drm/kernel.git
> 
> Still the same two branches. Can you please update the url? We haven't
> enabled the auto-mirror for this one, since we want to make sure the
> upgrade path in the tooling works and people do switch over to the new
> repo.

Done.  They seem to be fine.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-02-28 21:56 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 [this message]
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=20240229085628.44b5e53c@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=daniel@fooishbar.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox