Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Roy Kollen Svendsen <roykollensvendsen@gmail.com>
Cc: buildroot@buildroot.org,
	Andreas Naumann <ANaumann@ultratronik.de>,
	Christian Hitz <christian@klarinett.li>,
	Zoltan Gyarmati <zgyarmati@zgyarmati.de>,
	Jesse Van Gavere <jesseevg@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 1/2] package/qt6: bump version to 6.7.3
Date: Mon, 28 Oct 2024 22:43:05 +0100	[thread overview]
Message-ID: <20241028224305.138c39f5@windsurf> (raw)
In-Reply-To: <20241004210919.3699625-1-roykollensvendsen@gmail.com>

On Fri,  4 Oct 2024 23:09:16 +0200
Roy Kollen Svendsen <roykollensvendsen@gmail.com> wrote:

> For details see:
> 
> https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.7.3/release-note.md
> 
> I have removed a couple of patches here, since they are included in this
> version:
> 
>  - CVE-2024-39936  (qtbase)
>  - QTBUG-125066 Configure fails in qttools if PrintSupport is disabled  (qttools)
> 
> Signed-off-by: Roy Kollen Svendsen <roykollensvendsen@gmail.com>
> ---
> Notes v1:
>   qt 6.8.0 is going to be released in a few days, but I think it makes sense
>   to do this bump anyway, since there are a lot of bug fixes here that likely
>   can be safely backported

Applied 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

      parent reply	other threads:[~2024-10-28 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 21:09 [Buildroot] [PATCH v2 1/2] package/qt6: bump version to 6.7.3 Roy Kollen Svendsen
2024-10-04 21:09 ` [Buildroot] [PATCH v2 2/2] package/qt6/qt6charts: new package Roy Kollen Svendsen
2024-10-28 21:43   ` Thomas Petazzoni via buildroot
2024-10-28 21:43 ` 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=20241028224305.138c39f5@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ANaumann@ultratronik.de \
    --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