From: Colin Foster <colin.foster@in-advantage.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org,
Titouan Christophe <titouanchristophe@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/mosquitto: revert an upstream change in 2.0.20 breaking nonthread builds
Date: Mon, 9 Dec 2024 14:01:45 -0600 [thread overview]
Message-ID: <Z1dMqb2w12tpC51S@colin-ia-desktop> (raw)
In-Reply-To: <b8d9b247-6dc2-4193-b4fc-8a3feb0537cd@korsgaard.com>
On Mon, Dec 09, 2024 at 08:53:03PM +0100, Peter Korsgaard wrote:
> On 12/9/24 18:44, Colin Foster wrote:
> > Hi Peter,
> >
> > Out of curiosity, will there be a quick 2024.02.10 release with this or
> > will that come in the standard release cadence next month?
>
> How annoying is it? Are you using the git repo or a tarball? If git tree,
> can you use the 2024.02.9 tag + 1 commit instead?
I'm using the git tree. Yes, I think that'll work too.
> If needed, then I can do an early 2024.02.10 release, but it naturally has
> some overhead so I would prefer not to.
No need. I was just curious. Thanks for the quick response!
Colin Foster
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-12-09 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 7:43 [Buildroot] [PATCH] package/mosquitto: revert an upstream change in 2.0.20 breaking nonthread builds Peter Korsgaard
2024-12-07 9:51 ` Peter Korsgaard
2024-12-08 14:49 ` Peter Korsgaard
2024-12-09 9:23 ` Peter Korsgaard
2024-12-09 17:44 ` Colin Foster
2024-12-09 19:53 ` Peter Korsgaard
2024-12-09 20:01 ` Colin Foster [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=Z1dMqb2w12tpC51S@colin-ia-desktop \
--to=colin.foster@in-advantage.com \
--cc=buildroot@buildroot.org \
--cc=peter@korsgaard.com \
--cc=titouanchristophe@gmail.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