Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/{glibc, localedef}: bump to version 2.33-37-g162df872f0dfc2b124a18e1a8c33be63f70d9a1c
Date: Tue, 27 Apr 2021 13:36:31 +0200	[thread overview]
Message-ID: <87y2d4c62o.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <c5b1b792-4ac6-7452-eb36-8c8916413bf0@gmail.com> (Romain Naour's message of "Mon, 26 Apr 2021 23:19:42 +0200")

>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:

Hi,

 > For toolchain-builder project, this means that the stable and bleeding-edge
 > toolchain use the same glibc version, unlike for other toolchain elements.

But maybe the stable toolchain should be built from the Buildroot LTS
instead of the "bleeding edge" Buildroot version?

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2021-04-27 11:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 10:10 [Buildroot] [PATCH 1/2] package/localedef: bump to version 2.32-23 Romain Naour
2021-04-26 10:10 ` [Buildroot] [PATCH 2/2] package/{glibc, localedef}: bump to version 2.33-37-g162df872f0dfc2b124a18e1a8c33be63f70d9a1c Romain Naour
2021-04-26 19:36   ` Arnout Vandecappelle
2021-04-26 19:43     ` Yann E. MORIN
2021-04-27  7:25       ` Arnout Vandecappelle
2021-04-27  8:05         ` Romain Naour
     [not found]           ` <2BECD4AC-08A6-47CF-BA24-ED362C358095@c-sky.com>
2021-04-28 16:42             ` Romain Naour
2021-04-26 21:19     ` Romain Naour
2021-04-27  7:34       ` Arnout Vandecappelle
2021-04-27  8:37         ` Romain Naour
2021-04-27  8:44           ` Arnout Vandecappelle
2021-04-27  9:32             ` Romain Naour
2021-04-27 11:32         ` Peter Korsgaard
2021-04-27 11:36       ` Peter Korsgaard [this message]
2021-04-26 19:34 ` [Buildroot] [PATCH 1/2] package/localedef: bump to version 2.32-23 Arnout Vandecappelle
2021-04-26 21:05 ` Peter Korsgaard

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=87y2d4c62o.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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