all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 68321@debbugs.gnu.org, Munyoki Kilyungi <me@bonfacemunyoki.com>,
	Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
	Benjamin Slade <slade@lambda-y.net>, jgart <jgart@dismail.de>,
	"Paul A. Patience" <paul@apatience.com>
Subject: [bug#68321] Request for merging "lisp-team" branch
Date: Wed, 10 Jan 2024 22:10:25 +0000	[thread overview]
Message-ID: <878r4w7s5o.fsf@kitej> (raw)
In-Reply-To: <87cyu972rd.fsf@kitej>

[-- Attachment #1: Type: text/plain, Size: 319 bytes --]

Guillaume Le Vaillant <glv@posteo.net> skribis:

> Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> No need to wait for riscv64 for sbcl.
>
> Ok. I merged master in lisp-team, and if there are no new breakages,
> I'll merge lisp-team in master.

I just added a patch from upstream that should fix the riscv build.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2024-01-10 22:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 13:06 [bug#68321] Request for merging "lisp-team" branch Guillaume Le Vaillant
2024-01-08 18:12 ` Efraim Flashner
2024-01-09  0:35   ` Paul A. Patience
2024-01-09 14:10     ` Guillaume Le Vaillant
2024-01-09 16:59       ` Efraim Flashner
2024-01-09 17:36       ` Efraim Flashner
2024-01-09 20:24       ` Efraim Flashner
2024-01-10 10:45         ` Guillaume Le Vaillant
2024-01-10 11:01           ` Efraim Flashner
2024-01-10 13:08             ` Guillaume Le Vaillant
2024-01-10 22:10               ` Guillaume Le Vaillant [this message]
2024-01-11 13:50 ` 郑俊杰
2024-01-11 13:57   ` Guillaume Le Vaillant
2024-01-11 17:07     ` bug#68321: " Guillaume Le Vaillant

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=878r4w7s5o.fsf@kitej \
    --to=glv@posteo.net \
    --cc=68321@debbugs.gnu.org \
    --cc=cox.katherine.e+guix@gmail.com \
    --cc=efraim@flashner.co.il \
    --cc=jgart@dismail.de \
    --cc=me@bonfacemunyoki.com \
    --cc=paul@apatience.com \
    --cc=slade@lambda-y.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.
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.