From: Thomas Monjalon <thomas@monjalon.net>
To: jerinj@marvell.com, Jerin Jacob <jerinjacobk@gmail.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com,
david.marchand@redhat.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] doc: remove warning with doxygen 1.9.7
Date: Wed, 31 May 2023 16:01:24 +0200 [thread overview]
Message-ID: <3106713.TQGk6oTFT5@thomas> (raw)
In-Reply-To: <CALBAE1OD8_1F3ietNj_8p9krUgfdL54y3TwZ-OOdSzzTZ3ZuEA@mail.gmail.com>
31/05/2023 15:21, Jerin Jacob:
> On Wed, May 31, 2023 at 6:17 PM <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.
>
> loongarch-compilation reported a build issue at
> http://mails.dpdk.org/archives/test-report/2023-May/402940.html
> https://mesonbuild.com/Reference-manual_returned_external_program.html#external_programversion
> introduced in 0.62 version, so not sure how we can do version check
> without that.
>
> Another option is to just remove HTIML_TIMESTAMP from config file.
> Since 1.8.9 doxgen version,
> it is disabled by default.
>
> Thoughts?
No need to disable if it is already disabled by default.
What was the default of the old HTML_TIMESTAMP?
next prev parent reply other threads:[~2023-05-31 14:01 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 [this message]
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
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=3106713.TQGk6oTFT5@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.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 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).