From: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] doxygen: upgrade 1.17.0 -> 1.18.0
Date: Sun, 30 Aug 2026 00:07:52 -0700 [thread overview]
Message-ID: <2925873.1788073672353896461@lists.openembedded.org> (raw)
In-Reply-To: <CAGAhMBwE0G_1v=v50bCvtUPc_9NVzCs_o1wxOKD9f2zNK1FaJw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 163 bytes --]
Hi Robb,
No I didn't get this QA build path failure and may I know is there any prerequisite that trigger this ?
I built on Ubuntu 24.
Regrads,
Jaipaul
[-- Attachment #2: Type: text/html, Size: 241 bytes --]
next prev parent reply other threads:[~2026-08-30 7:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 12:20 [PATCH] doxygen: upgrade 1.17.0 -> 1.18.0 Jaipaul Cheernam
2026-08-29 20:19 ` [oe] " Rob Woolley
2026-08-30 7:07 ` Jaipaul Cheernam [this message]
2026-08-30 9:39 ` Rob Woolley
2026-08-30 10:50 ` Jaipaul Cheernam
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=2925873.1788073672353896461@lists.openembedded.org \
--to=jaipaul.cheernam@est.tech \
--cc=openembedded-devel@lists.openembedded.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