Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Zoltan Gyarmati <zgyarmati@zgyarmati.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/2] package/qt6/qt6core5compat: add new package
Date: Thu, 24 Aug 2023 23:18:23 +0200	[thread overview]
Message-ID: <20230824231823.62063121@windsurf> (raw)
In-Reply-To: <20230809171501.1329182-2-zgyarmati@zgyarmati.de>

On Wed,  9 Aug 2023 19:15:00 +0200
Zoltan Gyarmati <zgyarmati@zgyarmati.de> wrote:

> Signed-off-by: Zoltan Gyarmati <zgyarmati@zgyarmati.de>
> ---
>  package/qt6/Config.in                         |  1 +
>  package/qt6/qt6core5compat/Config.in          | 12 ++++++
>  .../qt6/qt6core5compat/qt6core5compat.hash    | 10 +++++
>  package/qt6/qt6core5compat/qt6core5compat.mk  | 39 +++++++++++++++++++
>  4 files changed, 62 insertions(+)
>  create mode 100644 package/qt6/qt6core5compat/Config.in
>  create mode 100644 package/qt6/qt6core5compat/qt6core5compat.hash
>  create mode 100644 package/qt6/qt6core5compat/qt6core5compat.mk

Applied to next after minor changes:

- Change commit title to "package/qt6/qt6core5compat: new package"

- Add an entry in the DEVELOPERS file

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

  reply	other threads:[~2023-08-24 21:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 17:14 [Buildroot] [PATCH v1 0/2] RFC Building packages both qt5/6 Zoltan Gyarmati
2023-08-09 17:15 ` [Buildroot] [PATCH v1 1/2] package/qt6/qt6core5compat: add new package Zoltan Gyarmati
2023-08-24 21:18   ` Thomas Petazzoni via buildroot [this message]
2023-08-09 17:15 ` [Buildroot] [PATCH v1 2/2] package/quazip: also enable for qt6 Zoltan Gyarmati
2023-08-24 21:19   ` Thomas Petazzoni 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=20230824231823.62063121@windsurf \
    --to=buildroot@buildroot.org \
    --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