From: Thomas Huth <thuth@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] docs/devel: Fix broken internal link to mailing lists
Date: Wed, 18 May 2022 09:04:35 +0200 [thread overview]
Message-ID: <ed9a8e2d-77e1-1f75-11d6-5f06488b2e98@redhat.com> (raw)
In-Reply-To: <20220315155426.659426-1-kchamart@redhat.com>
On 15/03/2022 16.54, Kashyap Chamarthy wrote:
> 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
Hi Kashyap!
This still seems to be broken - did you ever respin the other patches? (I
was not able to spot a v3 of the series...?)
Thomas
next prev parent reply other threads:[~2022-05-18 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 15:54 [PATCH] docs/devel: Fix broken internal link to mailing lists Kashyap Chamarthy
2022-05-18 7:04 ` Thomas Huth [this message]
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=ed9a8e2d-77e1-1f75-11d6-5f06488b2e98@redhat.com \
--to=thuth@redhat.com \
--cc=kchamart@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).