From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Roy Kollen Svendsen <roykollensvendsen@gmail.com>
Cc: buildroot@buildroot.org, Christian Hitz <christian@klarinett.li>,
Zoltan Gyarmati <zgyarmati@zgyarmati.de>,
Baxiche Su <baxiche@gmail.com>,
Jesse Van Gavere <jesseevg@gmail.com>
Subject: Re: [Buildroot] [PATCH 09/10] package/qt6/qt6tools: build only host linguist tools
Date: Sat, 17 May 2025 08:42:22 +0200 [thread overview]
Message-ID: <20250517084222.7b3a32f3@windsurf> (raw)
In-Reply-To: <CA+R_deo8cJVqYuPNiQdnXXbGuaY9o11rMYp1CsaRqVdfRSM_AQ@mail.gmail.com>
Hello Roy,
On Sat, 17 May 2025 07:18:19 +0200
Roy Kollen Svendsen <roykollensvendsen@gmail.com> wrote:
> fre. 16.
> > What does this mean?
> >
> The last sentence ended up there unintentionally during a rebase.
OK, that's what I thought :-)
> I think it is best to drop patch 10/10 for now. I can reintroduce that
> change when I need it.
>
> By the way, is 9/10 too large? Should we split the commit? Maybe it is
> better to gradually fix the concrete build failures than "starting
> from scratch?"
What are the concrete build failures being fixed? What are the
"on-going" issues that you are referring to. Keep in mind that we are
maintaining a LTS branch, to which we backport fixes so we really want
to understand when things broke, and therefore whether the fixes should
be backported.
Best regards,
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-05-17 6:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 10:36 [Buildroot] [PATCH 01/10] package/qt6: bump version to 6.9.0 Roy Kollen Svendsen
2025-05-15 10:36 ` [Buildroot] [PATCH 02/10] package/qt6/qt6connectivity: new package Roy Kollen Svendsen
2025-05-15 10:36 ` [Buildroot] [PATCH 03/10] package/qt6/qt6positioning: " Roy Kollen Svendsen
2025-05-15 10:36 ` [Buildroot] [PATCH 04/10] package/qt6/qt6grpc: " Roy Kollen Svendsen
2025-05-15 10:36 ` [Buildroot] [PATCH 05/10] package/qt6/qt6sensors: " Roy Kollen Svendsen
2025-05-15 10:36 ` [Buildroot] [PATCH 06/10] package/qt6/qt6speech: " Roy Kollen Svendsen
2025-05-15 10:36 ` [Buildroot] [PATCH 07/10] package/qt6/qt6base: fix build when xcb support is enabled Roy Kollen Svendsen
2025-05-31 16:57 ` Arnout Vandecappelle via buildroot
2025-05-15 10:36 ` [Buildroot] [PATCH 08/10] package/qt6/qt6multimedia: fix ffmpeg plugin build for x11 Roy Kollen Svendsen
2025-05-15 10:36 ` [Buildroot] [PATCH 09/10] package/qt6/qt6tools: build only host linguist tools Roy Kollen Svendsen
2025-05-16 20:51 ` Thomas Petazzoni via buildroot
2025-05-17 5:18 ` Roy Kollen Svendsen
2025-05-17 5:44 ` Roy Kollen Svendsen
2025-05-17 6:42 ` Thomas Petazzoni via buildroot [this message]
2025-05-17 16:48 ` Roy Kollen Svendsen
2025-05-19 21:13 ` Roy Kollen Svendsen
2025-05-20 5:13 ` Roy Kollen Svendsen
2025-05-15 10:36 ` [Buildroot] [PATCH 10/10] package/qt6/qt6tools: re-add basic target package Roy Kollen Svendsen
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=20250517084222.7b3a32f3@windsurf \
--to=buildroot@buildroot.org \
--cc=baxiche@gmail.com \
--cc=christian@klarinett.li \
--cc=jesseevg@gmail.com \
--cc=roykollensvendsen@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=zgyarmati@zgyarmati.de \
/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