From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>,
James Hilliard <james.hilliard1@gmail.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v7 5/5] package/json-glib: bump to version 1.10.6
Date: Mon, 13 Jan 2025 21:33:00 +0100 [thread overview]
Message-ID: <20250113213300.4ba5d4b8@windsurf> (raw)
In-Reply-To: <20250113200454.3108562-6-fiona.klute@gmx.de>
Hello,
On Mon, 13 Jan 2025 21:04:54 +0100
Fiona Klute <fiona.klute@gmx.de> wrote:
> From: "Fiona Klute (WIWA)" <fiona.klute@gmx.de>
>
> Fixes a build failure due to warnings from g-ir-scanner:
Does this happen due to the bump in PATCH 1/5 ? Does it happen already
before ? If it is happen due to the bump in PATCH 1/5, can this patch
be added *before* PATCH 1/5 in the series, i.e does it work with
earlier versions of glib/GOI ?
We're ideally trying to keep patch series and our commit history
"bisectable", i.e, every works between every patch. So when what patch
introduces an issue, we don't expect the issue to be fixed several
patches later.
Could you clarify this?
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:[~2025-01-13 20:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 20:04 [Buildroot] [PATCH v7 0/5] libglib2 2.82 series with bootstrap Fiona Klute via buildroot
2025-01-13 20:04 ` [Buildroot] [PATCH v7 1/5] package/{gobject-introspection, libglib2}: bump to {1.82.0, 2.82.4} Fiona Klute via buildroot
2025-01-13 20:04 ` [Buildroot] [PATCH v7 2/5] package/gobject-introspection: works with musl now Fiona Klute via buildroot
2025-01-13 20:29 ` Thomas Petazzoni
2025-01-13 20:56 ` Fiona Klute via buildroot
2025-01-13 20:04 ` [Buildroot] [PATCH v7 3/5] package/python-gobject: bump to version 3.50.0 Fiona Klute via buildroot
2025-01-13 20:30 ` Thomas Petazzoni via buildroot
2025-01-13 20:58 ` Fiona Klute via buildroot
2025-01-13 21:22 ` Thomas Petazzoni via buildroot
2025-01-13 21:40 ` Fiona Klute via buildroot
2025-01-13 22:16 ` Thomas Petazzoni via buildroot
2025-01-13 20:04 ` [Buildroot] [PATCH v7 4/5] package/network-manager: optional gobject-introspection Fiona Klute via buildroot
2025-01-13 20:31 ` Thomas Petazzoni
2025-01-13 21:02 ` Fiona Klute via buildroot
2025-01-13 21:23 ` Thomas Petazzoni via buildroot
2025-01-13 21:41 ` Fiona Klute via buildroot
2025-01-13 20:04 ` [Buildroot] [PATCH v7 5/5] package/json-glib: bump to version 1.10.6 Fiona Klute via buildroot
2025-01-13 20:33 ` Thomas Petazzoni via buildroot [this message]
2025-01-13 21:07 ` Fiona Klute via buildroot
2025-01-13 21:57 ` Fiona Klute 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=20250113213300.4ba5d4b8@windsurf \
--to=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=fiona.klute@gmx.de \
--cc=fontaine.fabrice@gmail.com \
--cc=james.hilliard1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox