From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Guillaume Le Vaillant <glv@posteo.net>,
Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: help-guix@gnu.org
Subject: Re: Heap space when building SBCL packages
Date: Tue, 24 Mar 2020 10:40:16 +0100 [thread overview]
Message-ID: <87h7ye6qgv.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87zhc6jgc1.fsf@yamatai>
[-- Attachment #1: Type: text/plain, Size: 57 bytes --]
Thanks!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-03-24 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 14:40 Heap space when building SBCL packages Konrad Hinsen
2020-03-23 14:59 ` Pierre Neidhardt
2020-03-23 17:06 ` Guillaume Le Vaillant
2020-03-23 17:17 ` Konrad Hinsen
2020-03-23 17:55 ` Pierre Neidhardt
2020-03-23 19:45 ` Konrad Hinsen
2020-03-23 20:30 ` Pierre Neidhardt
2020-03-24 7:40 ` Konrad Hinsen
2020-03-24 8:40 ` Guillaume Le Vaillant
2020-03-24 9:40 ` Pierre Neidhardt [this message]
2020-03-24 10:43 ` Konrad Hinsen
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7ye6qgv.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=glv@posteo.net \
--cc=help-guix@gnu.org \
--cc=konrad.hinsen@fastmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).