Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Quentin Schulz" <quentin.schulz@cherry.de>,
	"Quentin Schulz" <foss@0leil.net>,
	<openembedded-core@lists.openembedded.org>
Cc: "Antonin Godard" <antonin.godard@bootlin.com>
Subject: Re: [OE-core] [PATCH v3 1/2] python3-sphinxcontrib-svg2pdfconverter: add new recipe
Date: Wed, 03 Dec 2025 16:24:29 +0100	[thread overview]
Message-ID: <DEOOOYG9B8GR.21NMUE2VCUZ6A@bootlin.com> (raw)
In-Reply-To: <51ec8963-34b6-466d-9d16-10cb191036c9@cherry.de>

On Wed Dec 3, 2025 at 1:41 PM CET, Quentin Schulz wrote:
> Hi Mathieu,
>
>
> It says "Finished two hours ago" at the top of the provided link but I 
> sent v3 more recently than that.
>
> How do I know which patch(es) were applied from the logs? I went into 
> "Build properties" and it points at mathieu/master-next branch for 
> oe-core from openembedded-core-contrib repo at commit 
> 687147e96e53a1ddb3842a3d190a683161e82167 but this isn't the proper HEAD 
> anymore, so I had to start from commit 
> 687147e96e53a1ddb3842a3d190a683161e82167 from cgit and then go to its 
> parent recursively until I reached 
> https://git.openembedded.org/openembedded-core-contrib/commit/?h=mathieu/master-next&id=141b8fdfdc311053d69eab6adbec5c3b09e3acee 
> which is v2. Is there any chance we can have an easier way to figure 
> this out?
>
> I also ran the test locally with
>
> oe-selftest -r distrodata.Distrodata.test_maintainers
>
> and it passed.
>
> Cheers,
> Quentin

My bad, this was indeed an earlier revision:
https://git.yoctoproject.org/poky-ci-archive/commit/?h=oecore/autobuilder.yoctoproject.org/valkyrie/a-full-2814&id=141b8fdfdc311053d69eab6adbec5c3b09e3acee

Sorry for the noise.

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2025-12-03 15:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 11:32 [PATCH v3 0/2] buildtools-docs-tarball: add new Sphinx extension svg2pdfconverter Quentin Schulz
2025-12-03 11:32 ` [PATCH v3 1/2] python3-sphinxcontrib-svg2pdfconverter: add new recipe Quentin Schulz
2025-12-03 12:18   ` [OE-core] " Mathieu Dubois-Briand
2025-12-03 12:41     ` Quentin Schulz
2025-12-03 15:24       ` Mathieu Dubois-Briand [this message]
2025-12-03 11:32 ` [PATCH v3 2/2] buildtools-docs-tarball: add python3-sphinxcontrib-svg2pdfconverter to the SDK Quentin Schulz

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=DEOOOYG9B8GR.21NMUE2VCUZ6A@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=antonin.godard@bootlin.com \
    --cc=foss@0leil.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quentin.schulz@cherry.de \
    /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