From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Michael Nosthoff <buildroot@heine.tech>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/4] support/testing: sqlitecpp: new runtime test
Date: Sat, 10 Oct 2026 16:30:45 +0200 [thread overview]
Message-ID: <aspL3CWXADiYIzh2@windsurf> (raw)
In-Reply-To: <20261002075640.2350126-2-buildroot@heine.tech>
On Fri, Oct 02, 2026 at 09:56:30AM +0200, Michael Nosthoff via buildroot wrote:
> build and run an SQLiteCpp example to check database writes and queries.
>
> Assisted-by: GitHub Copilot:GPT-6 Sol
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
>
Thanks, entire series applied. I had to amend the commit logs for
PATCH 2/4 and 3/4 because it was missing the details on which commit
introduced the issue. I also pushed a minor fix commit to adjust the
Config.in comment that was incorrectly referring to C++11.
Best regards,
Thomas Petazzoni
--
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
prev parent reply other threads:[~2026-10-10 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 7:56 [Buildroot] [PATCH v2 1/4] support/testing: sqlitecpp: new runtime test Michael Nosthoff via buildroot
2026-10-02 7:56 ` [Buildroot] [PATCH v2 2/4] package/sqlitecpp: disable stack_protection Michael Nosthoff via buildroot
2026-10-07 8:00 ` Thomas Petazzoni via buildroot
2026-10-07 8:14 ` Michael Nosthoff via buildroot
2026-10-13 14:20 ` Thomas Petazzoni via buildroot
2026-10-02 7:56 ` [Buildroot] [PATCH v2 3/4] package/sqlitecpp: needs threads Michael Nosthoff via buildroot
2026-10-07 8:00 ` Thomas Petazzoni via buildroot
2026-10-02 7:56 ` [Buildroot] [PATCH v2 4/4] package/sqlitecpp: bump to version 3.4.0 Michael Nosthoff via buildroot
2026-10-10 14:30 ` 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=aspL3CWXADiYIzh2@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@heine.tech \
--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