From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maxime Ripard <mripard@redhat.com>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
David Airlie <airlied@gmail.com>
Cc: Daniel Stone <daniels@collabora.com>,
dim-tools@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: DRM Migration to Gitlab
Date: Tue, 27 Feb 2024 10:29:01 +0200 [thread overview]
Message-ID: <87edcyl38y.fsf@intel.com> (raw)
In-Reply-To: <k555c7lj3mcj2skzrmc2ywxzz5ndtdgfpitw7fftdlyjjpmfou@7maudk3vdxuf>
On Tue, 27 Feb 2024, Maxime Ripard <mripard@redhat.com> wrote:
> Hi,
>
> Sima, after becoming aware of the drm-misc transition to Gitlab in the
> next couple of weeks, to do the same for DRM today.
>
> This is now done and all the various bits (nightly.conf, MAINTAINERS,
> doc, etc.) should be there.
>
> If all goes well, the only thing you'll notice is that dim will complain
> about the drm remote not having the right URLs.
>
> Any dim user should update the URL with either one of the two following
> commands:
>
> git remote set-url drm ssh://git@gitlab.freedesktop.org/drm/kernel.git
> git remote set-url drm https://gitlab.freedesktop.org/drm/kernel.git
>
> And the rest should be transparent.
Except it isn't. If you do that before updating to new nightly.conf,
it'll complain that the URL it sees in the old config isn't available,
and prompts.
If you first do 'dim ub', and then do 'dim ub' again, before changing
the URL, it'll also prompt, but it's unable to override the existing drm
remote.
I think dim should be updated to handle all of this without user
manually doing anything other than answering a yes/no prompt.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-02-27 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 8:16 DRM Migration to Gitlab Maxime Ripard
2024-02-27 8:29 ` Jani Nikula [this message]
2024-02-27 9:18 ` Maxime Ripard
2024-02-27 12:09 ` Maxime Ripard
2024-02-27 19:03 ` Maxime Ripard
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=87edcyl38y.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mripard@redhat.com \
/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.