Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Knight <git@jdknight.me>
Cc: buildroot@buildroot.org, Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/3] package/libgtk3: remove schema compile hook
Date: Tue, 6 Jan 2026 23:03:50 +0100	[thread overview]
Message-ID: <20260106230350.0339a615@windsurf> (raw)
In-Reply-To: <20250809033757.1197-1-git@jdknight.me>

On Fri,  8 Aug 2025 23:37:55 -0400
James Knight <git@jdknight.me> wrote:

> Dropping the need for this package to compile any schemas as the
> libglib2 package (a dependency) already handles this during target
> finalization.
> 
> Signed-off-by: James Knight <git@jdknight.me>
> ---
>  package/libgtk3/libgtk3.mk | 7 -------
>  1 file changed, 7 deletions(-)

Thanks, series applied. Sorry that it took so long to apply this
obviously correct series.

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

      parent reply	other threads:[~2026-01-06 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-09  3:37 [Buildroot] [PATCH 1/3] package/libgtk3: remove schema compile hook James Knight
2025-08-09  3:37 ` [Buildroot] [PATCH 2/3] package/libgtk4: " James Knight
2026-01-19 10:09   ` Arnout Vandecappelle via buildroot
2025-08-09  3:37 ` [Buildroot] [PATCH 3/3] package/gvfs: remove schema compile and cleanup hook James Knight
2026-01-19 10:08   ` Arnout Vandecappelle via buildroot
2026-01-06 22:03 ` 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=20260106230350.0339a615@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=git@jdknight.me \
    --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