From: Luca Boccassi <bluca@debian.org>
To: David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Kevin Traynor <ktraynor@redhat.com>,
dpdk stable <stable@dpdk.org>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] doc: fix API index
Date: Thu, 28 May 2020 11:04:40 +0100 [thread overview]
Message-ID: <a8cc715d30819a114602abe1a3be01b0c4afaaa5.camel@debian.org> (raw)
In-Reply-To: <CAJFAV8wvsUOsxU8vwhRotq6iYhT+biw5U1QfBjq5v9kSB0sfqA@mail.gmail.com>
On Thu, 2020-05-28 at 11:14 +0200, David Marchand wrote:
> On Wed, May 27, 2020 at 2:17 PM David Marchand
> <david.marchand@redhat.com> wrote:
> > > With Doxygen 1.8.18, a warning appears when tagging
> > > the main markdown header with {#index}.
> > > That's why the tag has been removed from the API index in DPDK 20.05.
> > > Unfortunately it makes the index page classified as a standard
> > > "related page" instead of being the "main page".
> > >
> > > The tag {#mainpage} could be used instead of {#index}.
> > > Another solution, chosen here, is to specify the main page file
> > > in the Doxygen configuration with the variable USE_MDFILE_AS_MAINPAGE.
> > >
> > > Fixes: 76fb8fc486f9 ("doc: fix build with doxygen 1.8.18")
> > > Cc: stable@dpdk.org
> > >
> > > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > Tested-by: David Marchand <david.marchand@redhat.com>
>
> Applied, thanks.
>
> Luca, I saw you marked 76fb8fc486f9 ("doc: fix build with doxygen
> 1.8.18") for 19.11.3.
> So this current patch is a candidate for 19.11.3 too.
Already applied on suggestion from Thomas, thanks
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2020-05-28 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 20:29 [dpdk-dev] " Thomas Monjalon
2020-05-27 12:17 ` David Marchand
2020-05-28 9:14 ` David Marchand
2020-05-28 10:04 ` Luca Boccassi [this message]
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=a8cc715d30819a114602abe1a3be01b0c4afaaa5.camel@debian.org \
--to=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=marko.kovacevic@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).