From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>,
Matt Weber <matthew.weber@collins.com>,
Aleksander Morgado <aleksander@aleksander.es>,
buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v3] package/libqmi: bump to version 1.30.0
Date: Thu, 26 Aug 2021 14:43:29 +0200 [thread overview]
Message-ID: <20210826144329.768936d7@windsurf> (raw)
In-Reply-To: <CAGm1_kuW=EYjpXAL3g2mZhBxh4tAyB8633D+49Wiwij8-JbspA@mail.gmail.com>
Hello Yegor,
On Thu, 26 Aug 2021 06:01:07 +0200
Yegor Yefremov <yegorslists@googlemail.com> wrote:
> > Are you sure it is still fixing this issue ? I already made the same
> > comment on v2, pointing other commits that fixed gobject-introspection
> > issues.
>
> OK. I'll remove this comment. Though in the context of the next
> branch, it really fixes the compilation issue. The general fix is only
> in the master branch. libqrtr-glib still fails in the next branch.
Everything that is in the master branch will appear in the next branch,
either when if we merge master into next, or when 2021.08 is released
and we merge next back into master, and kill the next branch.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-08-26 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 9:02 [Buildroot] [PATCH v3] package/libqmi: bump to version 1.30.0 yegorslists--- via buildroot
2021-08-25 22:29 ` Thomas Petazzoni
2021-08-26 4:01 ` Yegor Yefremov via buildroot
2021-08-26 4:01 ` Yegor Yefremov
2021-08-26 12:43 ` Thomas Petazzoni [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=20210826144329.768936d7@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=aleksander@aleksander.es \
--cc=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=matthew.weber@collins.com \
--cc=yegorslists@googlemail.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