From: Petr Vorel <petr.vorel@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ima-evm-utils: bump version to 1.6.2
Date: Tue, 3 Sep 2024 23:15:04 +0200 [thread overview]
Message-ID: <20240903211504.GA817719@pevik> (raw)
In-Reply-To: <20240903230222.0019371b@windsurf>
Hi Thomas,
> On Mon, 2 Sep 2024 20:17:42 +0200
> Petr Vorel <petr.vorel@gmail.com> wrote:
> > This version also reintroduced COPYING COPYING.LGPL, therefore add them
> > to IMA_EVM_UTILS_LICENSE_FILES.
> It would have been good to explain here why the LICENSES.txt file gets
> changed (since you change its hash).
> I fixed that up with an explanation (after diffing the file
> before/after), and applied to next. Thanks a lot!
Thanks a lot for review and (again) improving my patch!
Kind regards,
Petr
> Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-09-03 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 18:17 [Buildroot] [PATCH 1/1] package/ima-evm-utils: bump version to 1.6.2 Petr Vorel
2024-09-03 21:02 ` Thomas Petazzoni via buildroot
2024-09-03 21:15 ` Petr Vorel [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=20240903211504.GA817719@pevik \
--to=petr.vorel@gmail.com \
--cc=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