All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: thomas.devoogdt@barco.com, christian@aperture.us,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] package/yq: add new package
Date: Sun, 28 Dec 2025 15:48:42 +0100	[thread overview]
Message-ID: <20251228154842.29feb75b@windsurf> (raw)
In-Reply-To: <20251201112621.242137-1-thomas@devoogdt.com>

Hello Thomas,

On Mon,  1 Dec 2025 12:26:20 +0100
Thomas Devoogdt <thomas@devoogdt.com> wrote:

> From: Thomas Devoogdt <thomas.devoogdt@barco.com>
> 
> Version 4.45.2 was selected as newer versions require Go 1.24 [1],
> which is not yet available in Buildroot 2025.02.x.
> 
> [1] https://github.com/mikefarah/yq/commit/5bc2cd03da9139160db70901ffb8002bf6e242d5
> 
> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>

Thanks, both patches applied, but squashed into a single patch. Indeed,
there's no point in adding a new package and bumping it right after.

Thanks a lot!

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:[~2025-12-28 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18 14:53 [Buildroot] [PATCH] package/yq: add new package Thomas Devoogdt
2025-11-18 15:52 ` Edgar Bonet via buildroot
2025-11-18 16:19   ` Thomas Devoogdt
2025-11-18 19:52     ` Edgar Bonet via buildroot
2025-11-30 16:44 ` Peter Korsgaard
2025-12-01 11:26   ` [Buildroot] [PATCH v2 1/2] " Thomas Devoogdt
2025-12-01 11:26     ` [Buildroot] [PATCH v2 2/2] package/yq: bump to 4.49.2 Thomas Devoogdt
2025-12-28 14:48     ` 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=20251228154842.29feb75b@windsurf \
    --to=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --cc=thomas.devoogdt@barco.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=thomas@devoogdt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.