All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com
Subject: [qemu-web PATCH] update links to the SubmitAPatch wiki page
Date: Thu, 18 Nov 2021 08:47:02 +0100	[thread overview]
Message-ID: <20211118074702.216951-2-pbonzini@redhat.com> (raw)

The page is now part of the documentation, but it also has a redirect
in the qemu.org web server to provide a stable URL.  Use it instead
of linking out to wiki.qemu.org.

Signed-off-by: Paolo Bonzini <pbonzini@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..6edc07b 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.org/contribute/submit-a-patch/
 
 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..856e434 100644
--- a/contribute.md
+++ b/contribute.md
@@ -17,6 +17,6 @@ permalink: /contribute/
   &ldquo;[Contributor FAQ](https://wiki.qemu.org/Contribute/FAQ)&rdquo;,
   &ldquo;[Improve the website](https://www.qemu.org/2017/02/04/the-new-qemu-website-is-up/)&rdquo;
 
-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](/submit-a-patch/).
 
 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..8d7d371 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](../submit-a-patch).
 
 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.33.1



             reply	other threads:[~2021-11-18  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18  7:47 Paolo Bonzini [this message]
2021-11-18  7:54 ` [qemu-web PATCH] update links to the SubmitAPatch wiki page Thomas Huth
2021-11-18 10:45 ` Daniel P. Berrangé

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=20211118074702.216951-2-pbonzini@redhat.com \
    --to=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 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.