From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
Cc: Bernd Kuhls <bernd@kuhls.net>,
Kadambini Nema <kadambini.nema@gmail.com>,
Marcus Hoffmann <buildroot@bubu1.eu>,
Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/{libuv, uvw}: bump version to libuv 1.47.0 and uvw 3.3.0
Date: Sat, 13 Jul 2024 00:03:36 +0200 [thread overview]
Message-ID: <20240713000336.501eb3b0@windsurf> (raw)
In-Reply-To: <552ccb1d-1be8-4ec0-8ea4-70d2de771cdb@bubu1.eu>
Hello Marcus,
On Thu, 22 Feb 2024 14:20:02 +0100
Marcus Hoffmann via buildroot <buildroot@buildroot.org> wrote:
> I think one patch per package update is preferred for buildroot. If one
> update depends on another one, these should be send in one series, but
> still as separate patches.
In the general case, you're right, but libuv/uvw are kind of special,
as the comment in libuv.mk indicates:
# When bumping libuv, check if a new version of uvw is available
# and bump it too.
So we do expect both to be updated together.
Best regards,
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:[~2024-07-12 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 22:46 [Buildroot] [PATCH 1/1] package/{libuv, uvw}: bump version to libuv 1.47.0 and uvw 3.3.0 Kadambini Nema
2024-02-22 13:20 ` Marcus Hoffmann via buildroot
2024-07-12 22:03 ` Thomas Petazzoni via buildroot [this message]
2024-07-12 22:02 ` Thomas Petazzoni 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=20240713000336.501eb3b0@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=bernd@kuhls.net \
--cc=buildroot@bubu1.eu \
--cc=kadambini.nema@gmail.com \
--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