From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel Berrange" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [qemu-web PATCH v2] Use GitLab repo URLs instead of git.qemu.org URLs
Date: Thu, 14 Jan 2021 12:07:25 +0100 [thread overview]
Message-ID: <98b537fa-9d9f-9005-359c-b1180b0e8f90@redhat.com> (raw)
In-Reply-To: <20210113185403.276395-1-stefanha@redhat.com>
On 1/13/21 7:54 PM, Stefan Hajnoczi wrote:
> Switch to GitLab repo URLs to reduce qemu.org bandwidth.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> v2:
> * Added missing URL in _posts/2018-06-28-tcg-testing.md. Mark
> Cave-Ayland <mark.cave-ayland@ilande.co.uk> and Alex Bennée
> <alex.bennee@linaro.org> figured out the issue was that the gitweb
> link referenced a blob object (not a commit) whereas GitLab needs the
> commit object. Therefore the hash hash in the URL has changed.
> ---
> _download/source.html | 4 ++--
> _posts/2017-02-04-the-new-qemu-website-is-up.md | 8 ++++----
> _posts/2017-10-04-qemu-2-10-1.md | 4 ++--
> _posts/2018-02-09-understanding-qemu-devices.md | 2 +-
> _posts/2018-06-28-tcg-testing.md | 4 ++--
> contribute.md | 2 +-
> contribute/security-process.md | 4 ++--
> documentation.md | 2 +-
> support.md | 2 +-
> 9 files changed, 16 insertions(+), 16 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2021-01-14 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 18:54 [qemu-web PATCH v2] Use GitLab repo URLs instead of git.qemu.org URLs Stefan Hajnoczi
2021-01-14 9:42 ` Thomas Huth
2021-01-14 13:40 ` Stefan Hajnoczi
2021-01-14 15:29 ` Thomas Huth
2021-01-14 16:21 ` Stefan Hajnoczi
2021-01-14 11:07 ` Philippe Mathieu-Daudé [this message]
2021-01-14 11:44 ` Alex Bennée
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=98b537fa-9d9f-9005-359c-b1180b0e8f90@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@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).