From: Kashyap Chamarthy <kchamart@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Kashyap Chamarthy <kchamart@redhat.com>
Subject: [qemu-web PATCH] Update URLs of "SubmitAPatch" wiki doc
Date: Thu, 18 Nov 2021 18:00:28 +0100 [thread overview]
Message-ID: <20211118170028.820558-1-kchamart@redhat.com> (raw)
We've recently converted[1] the "SubmitAPatch" page from Wiki to in-tree
docs. So update the website to reflect this.
[1] https://gitlab.com/qemu-project/qemu/-/commit/9f73de8df03 --
9f73de8df0 (docs: rSTify the "SubmitAPatch" wiki, 2021-11-10)
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
---
CONTRIBUTING.md | 2 +-
contribute.md | 2 +-
contribute/report-a-bug.md | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d5cbf07..b6fc0bd 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -12,7 +12,7 @@ You should also CC the website maintainers:
For further guidance on sending patches consult:
-https://wiki.qemu.org/Contribute/SubmitAPatch
+https://qemu-project.gitlab.io/qemu/devel/submitting-a-patch.html
It is expected that contributors check the rendered website before submitting
patches. This is possible by either running jekyll locally, or by using the
diff --git a/contribute.md b/contribute.md
index 4802452..77cd5f4 100644
--- a/contribute.md
+++ b/contribute.md
@@ -17,6 +17,6 @@ permalink: /contribute/
“[Contributor FAQ](https://wiki.qemu.org/Contribute/FAQ)”,
“[Improve the website](https://www.qemu.org/2017/02/04/the-new-qemu-website-is-up/)”
-Please do not submit merge requests on GitLab; patches are sent to the mailing list according to QEMU's [patch submissions guidelines](https://wiki.qemu.org/Contribute/SubmitAPatch).
+Please do not submit merge requests on GitLab; patches are sent to the mailing list according to QEMU's [patch submissions guidelines](https://qemu-project.gitlab.io/qemu/devel/submitting-a-patch.html).
Contributing to QEMU is subject to the [QEMU Code of Conduct](https://qemu.org/docs/master/devel/code-of-conduct.html).
diff --git a/contribute/report-a-bug.md b/contribute/report-a-bug.md
index 96b60d8..b24c759 100644
--- a/contribute/report-a-bug.md
+++ b/contribute/report-a-bug.md
@@ -18,7 +18,7 @@ When submitting a bug report, please try to do the following:
* Include information about the host and guest (operating system, version, 32/64-bit).
-QEMU does not use GitLab merge requests; patches are sent to the mailing list according to QEMU's [patch submissions guidelines](https://wiki.qemu.org/Contribute/SubmitAPatch).
+QEMU does not use GitLab merge requests; patches are sent to the mailing list according to QEMU's [patch submissions guidelines](https://qemu-project.gitlab.io/qemu/devel/submitting-a-patch.html).
Do NOT report security issues (or other bugs, too) as "confidential" bugs in the
bug tracker. QEMU has a [security process](../security-process) for issues
--
2.31.1
next reply other threads:[~2021-11-18 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 17:00 Kashyap Chamarthy [this message]
2021-11-19 9:09 ` [qemu-web PATCH] Update URLs of "SubmitAPatch" wiki doc Paolo Bonzini
2021-11-19 10:15 ` Other pages for docs/devel/ [Was: Re: ... Update URLs of "SubmitAPatch" ...] Kashyap Chamarthy
2021-11-24 19:35 ` Paolo Bonzini
2021-11-25 9:56 ` Kashyap Chamarthy
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=20211118170028.820558-1-kchamart@redhat.com \
--to=kchamart@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).