From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/libzenoh-pico: bump version to 1.0.0
Date: Tue, 22 Oct 2024 22:29:41 +0200 [thread overview]
Message-ID: <20241022222941.3720b546@windsurf> (raw)
In-Reply-To: <AS1P250MB06084A83D030B95E26EF7746A94C2@AS1P250MB0608.EURP250.PROD.OUTLOOK.COM>
On Tue, 22 Oct 2024 06:39:30 +0000
Michel Alex <Alex.Michel@wiedemann-group.com> wrote:
> https://github.com/eclipse-zenoh/zenoh-pico/releases/tag/1.0.0
> Signed-off-by: Alex Michel <alex.michel@wiedemann-group.com>
> ---
> package/libzenoh-pico/libzenoh-pico.hash | 2 +-
> package/libzenoh-pico/libzenoh-pico.mk | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
Both applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-10-22 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 6:39 [Buildroot] [PATCH 1/2] package/libzenoh-pico: bump version to 1.0.0 Michel Alex
2024-10-22 20:29 ` Thomas Petazzoni via buildroot [this message]
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=20241022222941.3720b546@windsurf \
--to=buildroot@buildroot.org \
--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