From: Kashyap Chamarthy <kchamart@redhat.com>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, Kashyap Chamarthy <kchamart@redhat.com>
Subject: [PATCH] docs/devel: Fix broken internal link to mailing lists
Date: Tue, 15 Mar 2022 16:54:26 +0100 [thread overview]
Message-ID: <20220315155426.659426-1-kchamart@redhat.com> (raw)
Missed this during the initial conversion.
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
---
This patch should be merged on top of this[1]. Otherwise Sphinx will
complain (correctly so).
[1] https://lists.nongnu.org/archive/html/qemu-devel/2022-03/msg03488.html
-- docs: rSTify MailingLists wiki; move it to QEMU Git
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
---
docs/devel/submitting-a-patch.rst | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/devel/submitting-a-patch.rst b/docs/devel/submitting-a-patch.rst
index e51259eb9c..3632b74585 100644
--- a/docs/devel/submitting-a-patch.rst
+++ b/docs/devel/submitting-a-patch.rst
@@ -18,13 +18,13 @@ one-shot fix, the bare minimum we ask is that:
<http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches?id=f6f94e2ab1b33f0082ac22d71f66385a60d8157f#n297>`__
policy.) ``git commit -s`` or ``git format-patch -s`` will add one.
- All contributions to QEMU must be **sent as patches** to the
- qemu-devel `mailing list <MailingLists>`__. Patch contributions
- should not be posted on the bug tracker, posted on forums, or
- externally hosted and linked to. (We have other mailing lists too,
- but all patches must go to qemu-devel, possibly with a Cc: to another
- list.) ``git send-email`` (`step-by-step setup
- guide <https://git-send-email.io/>`__ and `hints and
- tips <https://elixir.bootlin.com/linux/latest/source/Documentation/process/email-clients.rst>`__)
+ qemu-devel mailing list (refer to :ref:`mailing-lists`). Patch
+ contributions should not be posted on the bug tracker, posted on
+ forums, or externally hosted and linked to. (We have other mailing
+ lists too, but all patches must go to qemu-devel, possibly with a Cc:
+ to another list.) ``git send-email`` (`step-by-step setup guide
+ <https://git-send-email.io/>`__ and `hints and tips
+ <https://elixir.bootlin.com/linux/latest/source/Documentation/process/email-clients.rst>`__)
works best for delivering the patch without mangling it, but
attachments can be used as a last resort on a first-time submission.
- You must read replies to your message, and be willing to act on them.
--
2.33.1
next reply other threads:[~2022-03-15 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 15:54 Kashyap Chamarthy [this message]
2022-05-18 7:04 ` [PATCH] docs/devel: Fix broken internal link to mailing lists Thomas Huth
2022-05-18 8:04 ` 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=20220315155426.659426-1-kchamart@redhat.com \
--to=kchamart@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.