From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Joachim Wiberg <troglobit@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 2/2] package/libite: bump to v2.6.2
Date: Wed, 4 Feb 2026 14:14:12 +0100 [thread overview]
Message-ID: <aYNGAIULEA-4DYt3@windsurf> (raw)
In-Reply-To: <20251216093534.2558659-2-troglobit@gmail.com>
Hello Joachim,
On Tue, Dec 16, 2025 at 10:35:34AM +0100, Joachim Wiberg wrote:
> # Locally calculated
> sha256 3a2b964c1772d03ab17b73a389ecce9151e0b190a9247817a2c009b16d356422 LICENSE
> sha256 c2882adb51555b836f35babc59f618d9ddceadcaa2d1dc80bbd4699614d2cd14 src/chomp.c
> -sha256 bff7fa7b74324f13a24d56ebb8b49bc9c63ea01836a1c8b5a6afcbbabed62918 src/pidfile.c
> +sha256 b6cc7074a27b26ee4e1ccda8d634d485d0f6f819e564c663c28ed61f4cc2b451 src/pidfile.c
We normally require changes to license files to be explained in the
commit message, so I've amended the commit message with some details
about this and applied.
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-02-04 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 9:35 [Buildroot] [PATCH v2 1/2] package/libite: fix missing deps, requires fork() Joachim Wiberg
2025-12-16 9:35 ` [Buildroot] [PATCH v2 2/2] package/libite: bump to v2.6.2 Joachim Wiberg
2026-02-04 13:14 ` Thomas Petazzoni via buildroot [this message]
2026-02-13 19:37 ` Thomas Perale via buildroot
2026-02-04 13:13 ` [Buildroot] [PATCH v2 1/2] package/libite: fix missing deps, requires fork() Thomas Petazzoni via buildroot
2026-02-13 19:37 ` Thomas Perale 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=aYNGAIULEA-4DYt3@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=troglobit@gmail.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