From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Julien Olivain <ju.o@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/python-memray: require toolchain with C++ support
Date: Mon, 5 Jan 2026 17:05:47 +0100 [thread overview]
Message-ID: <20260105170547.6f767364@windsurf> (raw)
In-Reply-To: <9bff7357-ef32-4d03-873e-7d052655158b@gmx.de>
Hello Fiona,
On Mon, 5 Jan 2026 15:42:33 +0100
Fiona Klute <fiona.klute@gmx.de> wrote:
> I've just sent v2 of the series that should address both issues.
It does, thanks!
You can also just use the Fixes tag:
Fixes: 26bc4b51a808d73c09598035aa94f9c37b273218 ("package/python-rich: new package")
No need to resend just for that, that's merely a suggestion for future
commits.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-01-05 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 14:32 [Buildroot] [PATCH 1/2] package/python-rich: add missing dependency on zlib support in Python Fiona Klute via buildroot
2026-01-04 14:32 ` [Buildroot] [PATCH 2/2] package/python-memray: require toolchain with C++ support Fiona Klute via buildroot
2026-01-04 16:46 ` Thomas Petazzoni via buildroot
2026-01-05 14:42 ` Fiona Klute via buildroot
2026-01-05 16:05 ` Thomas Petazzoni via buildroot [this message]
2026-01-04 16:45 ` [Buildroot] [PATCH 1/2] package/python-rich: add missing dependency on zlib support in Python Thomas Petazzoni via buildroot
2026-01-04 16:54 ` Fiona Klute via buildroot
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=20260105170547.6f767364@windsurf \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=james.hilliard1@gmail.com \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
/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