qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Daniel Berrange" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH 4/6] docs: update README to use GitLab repo URLs
Date: Mon, 11 Jan 2021 11:50:15 +0000	[thread overview]
Message-ID: <20210111115017.156802-5-stefanha@redhat.com> (raw)
In-Reply-To: <20210111115017.156802-1-stefanha@redhat.com>

qemu.org is running out of bandwidth and the QEMU project is moving
towards a gating CI on GitLab. Use the GitLab repos instead of qemu.org
(they will become mirrors).

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 README.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.rst b/README.rst
index 58b9f2dc15..ce39d89077 100644
--- a/README.rst
+++ b/README.rst
@@ -60,7 +60,7 @@ The QEMU source code is maintained under the GIT version control system.
 
 .. code-block:: shell
 
-   git clone https://git.qemu.org/git/qemu.git
+   git clone https://gitlab.com/qemu-project/qemu.git
 
 When submitting patches, one common approach is to use 'git
 format-patch' and/or 'git send-email' to format & send the mail to the
@@ -78,7 +78,7 @@ The QEMU website is also maintained under source control.
 
 .. code-block:: shell
 
-  git clone https://git.qemu.org/git/qemu-web.git
+  git clone https://gitlab.com/qemu-project/qemu-web.git
 
 * `<https://www.qemu.org/2017/02/04/the-new-qemu-website-is-up/>`_
 
-- 
2.29.2


  parent reply	other threads:[~2021-01-11 11:56 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
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 ` Stefan Hajnoczi [this message]
2021-01-12  7:56   ` [PATCH 4/6] docs: update README to use GitLab repo URLs 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=20210111115017.156802-5-stefanha@redhat.com \
    --to=stefanha@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=thuth@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).