From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Stone <daniel@fooishbar.org>
Cc: Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org, 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: Wed, 21 Feb 2024 09:46:43 +1100 [thread overview]
Message-ID: <20240221094643.4496313a@canb.auug.org.au> (raw)
In-Reply-To: <CAPj87rMYC3D-PYtMcTXD3=HqNSpyyVj9jp0nodO+2PebP1guAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]
Hi Daniel,
On Tue, 20 Feb 2024 11:25:05 +0000 Daniel Stone <daniel@fooishbar.org> wrote:
>
> On Tue, 20 Feb 2024 at 09:05, Maxime Ripard <mripard@kernel.org> wrote:
> > On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> > > 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.
>
> cc sfr - once we move the DRM repos to a different location, what's
> the best way to update linux-next?
>
> That being said, we could set up read-only pull mirrors in the old
> location ... something I want to do in March (because what else are
> you going to do on holiday?) is to kill the write repos on kemper
> (git.fd.o), move them to being on molly (cgit/anongit.fd.o) only, and
> just have a cronjob that regularly pulls from all the gl.fd.o repos,
> rather than pushing from GitLab.
These are (I think) all the drm trees/branches that I fetch every day:
git://anongit.freedesktop.org/drm-intel#for-linux-next
git://anongit.freedesktop.org/drm-intel#for-linux-next-fixes
git://anongit.freedesktop.org/drm/drm-misc#for-linux-next
git://anongit.freedesktop.org/drm/drm-misc#for-linux-next-fixes
git://git.freedesktop.org/git/drm/drm.git#drm-fixes
git://git.freedesktop.org/git/drm/drm.git#drm-next
git://git.freedesktop.org/git/drm/drm.git#topic/drm-ci
git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git#for-linux-next
https://gitlab.freedesktop.org/agd5f/linux#drm-next
https://gitlab.freedesktop.org/drm/msm.git#msm-next
https://gitlab.freedesktop.org/drm/tegra.git#for-next
https://gitlab.freedesktop.org/lumag/msm.git#msm-next-lumag
If someone could just send me all the new equivalent URLs when the
change happens, I will fix them up in my config.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-02-20 22:46 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 [this message]
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=20240221094643.4496313a@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 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.