From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adrian Perez de Castro <aperez@igalia.com>
Cc: Raphael Pavlidis <raphael.pavlidis@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/3] package/cage: bump to version 0.1.5
Date: Wed, 1 Nov 2023 12:03:48 +0100 [thread overview]
Message-ID: <20231101120348.38b1e18d@windsurf> (raw)
In-Reply-To: <20231030101115.2214402-3-aperez@igalia.com>
On Mon, 30 Oct 2023 12:11:06 +0200
Adrian Perez de Castro <aperez@igalia.com> wrote:
> Update Cage to version 0.1.5, which is a bug fix release that
> supports using wlroots 0.16.x.
>
> Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
> ---
> .../cage/0001-Upgrade-to-wlroots-0.15.patch | 312 ------------------
> package/cage/cage.hash | 4 +-
> package/cage/cage.mk | 2 +-
> 3 files changed, 3 insertions(+), 315 deletions(-)
> delete mode 100644 package/cage/0001-Upgrade-to-wlroots-0.15.patch
You had forgotten to update the .checkpackageignore file with the
removed patch, so I did that when applying to master. 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
next prev parent reply other threads:[~2023-11-01 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 10:11 [Buildroot] [PATCH 0/3] Update wlroots to 0.16.x and dependent packages Adrian Perez de Castro
2023-10-30 10:11 ` [Buildroot] [PATCH 1/3] package/wlroots: bump to version 0.16.2 Adrian Perez de Castro
2023-11-01 11:03 ` Thomas Petazzoni via buildroot
2023-10-30 10:11 ` [Buildroot] [PATCH 2/3] package/cage: bump to version 0.1.5 Adrian Perez de Castro
2023-11-01 11:03 ` Thomas Petazzoni via buildroot [this message]
2023-10-30 10:11 ` [Buildroot] [PATCH 3/3] package/sway: bump to version 1.8.1 Adrian Perez de Castro
2023-11-01 11:03 ` 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=20231101120348.38b1e18d@windsurf \
--to=buildroot@buildroot.org \
--cc=aperez@igalia.com \
--cc=raphael.pavlidis@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.