patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: jerinj@marvell.com, dev@dpdk.org, thomas@monjalon.net, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] doc: remove warning with doxygen 1.9.7
Date: Fri, 2 Jun 2023 14:13:11 +0530	[thread overview]
Message-ID: <CALBAE1N1we9dFc+CvnGmpLgG_a2-=xGKcvhCuiK2BE5qpQEWMQ@mail.gmail.com> (raw)
In-Reply-To: <ZHmrQThBfGx78F8V@bricha3-MOBL.ger.corp.intel.com>

On Fri, Jun 2, 2023 at 2:11 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> On Fri, Jun 02, 2023 at 02:00:32PM +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 providing
> > the correct configuration option based on doxygen version.
> >
> > [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>
> > ---
> > v2:
> > - use run_command() as https://mesonbuild.com/Reference-manual_returned_external_program.html#external_programversion
> > introduced in 0.62 version and DPDK min meson version is 0.53.2
> >
> >  doc/api/doxy-api.conf.in | 2 +-
> >  doc/api/meson.build      | 7 +++++++
> >  2 files changed, 8 insertions(+), 1 deletion(-)
> >
> > diff --git a/doc/api/doxy-api.conf.in b/doc/api/doxy-api.conf.in
> > index d230a19e1f..60e582d8fc 100644
> > --- a/doc/api/doxy-api.conf.in
> > +++ b/doc/api/doxy-api.conf.in
> > @@ -111,7 +111,7 @@ GENERATE_DEPRECATEDLIST = YES
> >  VERBATIM_HEADERS        = NO
> >  ALPHABETICAL_INDEX      = NO
> >
> > -HTML_TIMESTAMP          = NO
> > +@TS_PREFIX@TIMESTAMP   = NO
>
> As explained in previous email, belately sent in reply to v1, I think we
> should just drop this line, and not worry about version checks.

Yes. I think that is better. I will send new version to remove it.

>
> /Bruce
>

  reply	other threads:[~2023-06-02  8:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 12:46 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 [this message]
2023-06-02 11:06   ` [dpdk-dev] [PATCH v3] " jerinj
2023-06-02 11:16     ` Bruce Richardson
2023-06-12 17:19       ` Thomas Monjalon

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='CALBAE1N1we9dFc+CvnGmpLgG_a2-=xGKcvhCuiK2BE5qpQEWMQ@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.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).