From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 1/6] .github: point Repo Lockdown bot to GitLab repo
Date: Tue, 12 Jan 2021 08:49:55 +0100 [thread overview]
Message-ID: <0db7e143-d31b-c067-716c-6a82fad60383@redhat.com> (raw)
In-Reply-To: <20210111115149.GC1172772@redhat.com>
On 11/01/2021 12.51, Daniel P. Berrangé wrote:
> On Mon, Jan 11, 2021 at 11:50:12AM +0000, Stefan Hajnoczi wrote:
>> Use the GitLab repo URL as the main repo location in order to reduce
>> load on qemu.org.
>>
>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>> ---
>> .github/lockdown.yml | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/.github/lockdown.yml b/.github/lockdown.yml
>> index 9acc393f1c..07fc2f31ee 100644
>> --- a/.github/lockdown.yml
>> +++ b/.github/lockdown.yml
>> @@ -10,8 +10,8 @@ issues:
>> comment: |
>> Thank you for your interest in the QEMU project.
>>
>> - This repository is a read-only mirror of the project's master
>> - repostories hosted on https://git.qemu.org/git/qemu.git.
>> + This repository is a read-only mirror of the project's repostories hosted
>> + at https://gitlab.com/qemu-project/qemu.git.
>
> NB this URL triggers a redirect to strip the .git suffix
>
> https://gitlab.com/qemu-project/qemu
If you try to do:
git clone https://gitlab.com/qemu-project/qemu
You get this warning message instead:
warning: redirecting to https://gitlab.com/qemu-project/qemu.git/
So I think the patch is fine.
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2021-01-12 7:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 11:50 [PATCH 0/6] Update git repo URLs to GitLab Stefan Hajnoczi
2021-01-11 11:50 ` [PATCH 1/6] .github: point Repo Lockdown bot to GitLab repo Stefan Hajnoczi
2021-01-11 11:51 ` Daniel P. Berrangé
2021-01-12 7:49 ` Thomas Huth [this message]
2021-01-12 10:33 ` Stefan Hajnoczi
2021-01-11 11:50 ` [PATCH 2/6] gitmodules: use GitLab repos instead of qemu.org Stefan Hajnoczi
2021-01-11 12:16 ` Philippe Mathieu-Daudé
2021-01-12 7:54 ` Thomas Huth
2021-01-11 11:50 ` [PATCH 3/6] gitlab-ci: remove redundant GitLab repo URL command Stefan Hajnoczi
2021-01-11 12:16 ` Philippe Mathieu-Daudé
2021-01-12 7:55 ` Thomas Huth
2021-01-11 11:50 ` [PATCH 4/6] docs: update README to use GitLab repo URLs Stefan Hajnoczi
2021-01-12 7:56 ` Thomas Huth
2021-01-11 11:50 ` [PATCH 5/6] pc-bios: update mirror URLs to GitLab Stefan Hajnoczi
2021-01-12 7:59 ` Thomas Huth
2021-01-11 11:50 ` [PATCH 6/6] get_maintainer: update repo URL " Stefan Hajnoczi
2021-01-11 12:18 ` Philippe Mathieu-Daudé
2021-01-12 8:01 ` Thomas Huth
2021-01-11 14:50 ` [PATCH 0/6] Update git repo URLs " Wainer dos Santos Moschetta
2021-01-21 14:56 ` Stefan Hajnoczi
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=0db7e143-d31b-c067-716c-6a82fad60383@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wainersm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).