From: Peter Korsgaard <peter@korsgaard.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libfuse3: bump to version 3.15.0
Date: Thu, 15 Jun 2023 08:51:10 +0200 [thread overview]
Message-ID: <874jn9md5t.fsf@48ers.dk> (raw)
In-Reply-To: <20230613190909.3873760-1-giulio.benetti@benettiengineering.com> (Giulio Benetti's message of "Tue, 13 Jun 2023 21:09:09 +0200")
>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:
> Drop local patch that has been upstreamed but add a new one to fix build
> failure:
> ../meson.build:180:12: ERROR: Can not run test applications in this
> cross environment.
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Committed after dropping the old patch from .checkpackageignore, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-06-15 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 19:09 [Buildroot] [PATCH] package/libfuse3: bump to version 3.15.0 Giulio Benetti
2023-06-15 6:51 ` Peter Korsgaard [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=874jn9md5t.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.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