From: Thomas Monjalon <thomas@monjalon.net>
To: Stanislaw Kardach <kda@semihalf.com>, john.mcnamara@intel.com
Cc: David Marchand <david.marchand@redhat.com>,
dev@dpdk.org, upstream@semihalf.com
Subject: Re: [PATCH] doc: fix formatting in RISC-V release notes entry
Date: Thu, 09 Jun 2022 15:30:42 +0200 [thread overview]
Message-ID: <16224896.geO5KgaWL5@thomas> (raw)
In-Reply-To: <20220609121747.716411-1-kda@semihalf.com>
09/06/2022 14:17, Stanislaw Kardach:
> There was an extra * in the title of the RISC-V entry. It gets rendered
> in the documentation output giving an impression that there will be a
> footnote for this entry, which is not the case.
>
> Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
> ---
> -* **Added initial RISC-V architecture support.***
> +* **Added initial RISC-V architecture support.**
We can fix it as part of the various release notes fix
that John is doing usually at the end of a cycle.
He will probably find more rewording around this.
next prev parent reply other threads:[~2022-06-09 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 12:17 Stanislaw Kardach
2022-06-09 13:30 ` Thomas Monjalon [this message]
2022-06-09 13:33 ` Stanisław Kardach
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=16224896.geO5KgaWL5@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=kda@semihalf.com \
--cc=upstream@semihalf.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).