From: Peter Korsgaard <peter@korsgaard.com>
To: yann.morin@orange.com
Cc: <buildroot@buildroot.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Vincent Fazio <vfazio@xes-inc.com>
Subject: Re: [Buildroot] [PATCH 0/2 v2] support/size-stats: actually handle .pyc files
Date: Thu, 17 Sep 2026 22:29:41 +0200 [thread overview]
Message-ID: <878q4zmxje.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <aqurjVe5-DeDVRh6@yd-6wlzhs3> (yann morin's message of "Thu, 17 Sep 2026 10:57:49 +0200")
>>>>> "yann" == yann morin <yann.morin@orange.com> writes:
> All,
> +Peter, +Thomas
> On 2026-09-14 14:48 +0200, yann.morin@orange.com spake thusly:
>> This small two-patch series properly associates .pyc files to the
>> corresponding package, to account for the PEP 3147 layout.
> Weird: this patch series did not end up in patchwork, although it is on
> lore:
> https://lore.kernel.org/buildroot/cover.1789390115.git.yann.morin@orange.com/
> Should I resend it?
It it certainly easier to have it in patchwork, please do.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-09-17 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 12:48 [Buildroot] [PATCH 0/2 v2] support/size-stats: actually handle .pyc files yann.morin
2026-09-14 12:48 ` [Buildroot] [PATCH 1/2 v2] support/scripts/size-stats: prepare for more .py associated files yann.morin
2026-09-14 12:48 ` [Buildroot] [PATCH 2/2 v2] support/scripts/size-stats: properly assign pre-compiled .pyc files yann.morin
2026-09-17 8:57 ` [Buildroot] [PATCH 0/2 v2] support/size-stats: actually handle " yann.morin
2026-09-17 20:29 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-18 4:45 yann.morin
2026-09-21 12:42 ` Vincent Fazio
2026-10-08 17:21 ` yann.morin
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=878q4zmxje.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vfazio@xes-inc.com \
--cc=yann.morin@orange.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