From: Thomas Monjalon <thomas@monjalon.net>
To: jerinj@marvell.com
Cc: dev@dpdk.org, stable@dpdk.org,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: remove warning with doxygen 1.9.7
Date: Mon, 12 Jun 2023 19:19:01 +0200 [thread overview]
Message-ID: <8786153.VV5PYv0bhD@thomas> (raw)
In-Reply-To: <ZHnPpE5MrtU6PP0i@bricha3-MOBL.ger.corp.intel.com>
02/06/2023 13:16, Bruce Richardson:
> On Fri, Jun 02, 2023 at 04:36:59PM +0530, jerinj@marvell.com wrote:
> > From: Jerin Jacob <jerinj@marvell.com>
> >
> > Since doxygen 1.9.7 version, HTML_TIMESTAMP configuration option
> > changed to TIMESTAMP [2]. Fixed the following warning[1] by
> > removing TIMESTAMP options all together as all new versions(since 1.8.9)
> > of doxygen this option is disabled by default. Another option was
> > considered to have this configuration option based on version check, which
> > may not be worth having it, especially, external_program.version()
> > API introduced in 0.62.0 version of meson.
> >
> > [1]
> > Warning: Tag 'HTML_TIMESTAMP' at line 115 of file 'doc/api/doxy-api.conf'
> > has become obsolete.
> >
> > [2]
> > https://www.doxygen.nl/manual/config.html#cfg_timestamp
> >
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks.
prev parent reply other threads:[~2023-06-12 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 12:46 [dpdk-dev] [PATCH v1] doc: remove warning with doxygen 1.9.7 jerinj
2023-05-31 13:21 ` Jerin Jacob
2023-05-31 14:01 ` Thomas Monjalon
2023-05-31 14:07 ` Jerin Jacob
2023-05-31 14:49 ` Thomas Monjalon
2023-05-31 14:54 ` Jerin Jacob
2023-05-31 15:06 ` Thomas Monjalon
2023-06-02 8:40 ` Bruce Richardson
2023-06-02 8:30 ` jerinj
2023-06-02 8:41 ` Bruce Richardson
2023-06-02 8:43 ` Jerin Jacob
2023-06-02 11:06 ` [dpdk-dev] [PATCH v3] " jerinj
2023-06-02 11:16 ` Bruce Richardson
2023-06-12 17:19 ` Thomas Monjalon [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=8786153.VV5PYv0bhD@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=stable@dpdk.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 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.