From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Leo Famulari <leo@famulari.name>,
Richard Sent <richard@freakingpenguin.com>
Cc: guix-devel@gnu.org, Ricardo Wurmus <rekado@elephly.net>,
Efraim Flashner <efraim@flashner.co.il>
Subject: Re: Does anyone use i686-linux? [was Re: bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux]
Date: Thu, 01 Aug 2024 16:51:40 -0700 [thread overview]
Message-ID: <87ikwj7qer.fsf@lease-up.com> (raw)
In-Reply-To: <Zqj7KEUwUBxBrw6R@jasmine.lan>
[dropped address for defect report]
Hi Leo,
On Tue, Jul 30 2024, Leo Famulari wrote:
> After years of watching the i686 kernel packages fail to build
Sorry to burden the list. A brief note about your and Wilko's tireless
but possibly under-appreciated commitment to kernels seemed in order.
Thank you!
Kind regards
Felix
next prev parent reply other threads:[~2024-08-01 23:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 20:55 bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux Leo Famulari
2023-12-06 12:25 ` Efraim Flashner
2024-07-26 18:51 ` Does anyone use i686-linux? [was Re: bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux] Leo Famulari
2024-07-26 20:17 ` Kaelyn
2024-07-28 21:49 ` Efraim Flashner
2024-07-29 12:33 ` Ricardo Wurmus
2024-07-29 15:00 ` Richard Sent
2024-07-30 0:01 ` Leo Famulari
2024-07-30 1:21 ` Richard Sent
2024-07-30 14:39 ` Leo Famulari
2024-08-01 23:51 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2024-07-30 15:18 ` Efraim Flashner
2024-07-30 21:02 ` bug#67535: " André Batista
2024-08-01 20:12 ` Leo Famulari
2024-08-02 8:36 ` Ricardo Wurmus
2024-08-02 19:34 ` bug#67535: " André Batista
2024-09-05 9:42 ` Ricardo Wurmus
2024-09-05 23:52 ` André Batista
2024-08-12 14:03 ` Ludovic Courtès
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=87ikwj7qer.fsf@lease-up.com \
--to=guix-devel@gnu.org \
--cc=efraim@flashner.co.il \
--cc=felix.lechner@lease-up.com \
--cc=leo@famulari.name \
--cc=rekado@elephly.net \
--cc=richard@freakingpenguin.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.