unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: guix-patches--- via <guix-patches@gnu.org>
To: <66723@debbugs.gnu.org>
Subject: [bug#66723] [PATCH 0/3] gnu: zig-0.10: Inherit from zig-0.9.
Date: Sun, 19 Nov 2023 20:35:13 +0900	[thread overview]
Message-ID: <CX2R5KPSM94S.223IA5MY5FJU2@guix> (raw)
In-Reply-To: <cover.1698134803.git.hako@ultrarare.space>

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

Should we keep Zig 0.9?  All currently packaged Zig programs
requires it anymore AFAICT, and the language is immature enough
I'd argue we should only keep older versions when necessary.

Your patchset adding LLVM 16 has been applied BTW,
I can't wait for Zig 0.11!

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

  parent reply	other threads:[~2023-11-19 11:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24  8:23 [bug#66723] [PATCH 0/3] gnu: zig-0.10: Inherit from zig-0.9 Hilton Chain via Guix-patches via
2023-10-24  8:34 ` [bug#66723] [PATCH 1/3] gnu: zig-0.10: Use gexp Hilton Chain via Guix-patches via
2023-10-24  8:34 ` [bug#66723] [PATCH 2/3] gnu: zig-0.9: " Hilton Chain via Guix-patches via
2023-10-24  8:34 ` [bug#66723] [PATCH 3/3] gnu: zig-0.10: Inherit from zig-0.9 Hilton Chain via Guix-patches via
2023-11-19 11:35 ` guix-patches--- via [this message]
2023-11-23 15:23   ` [bug#66723] [PATCH 0/3] " Hilton Chain via Guix-patches via
2023-11-23 16:23     ` Ekaitz Zarraga
2023-11-25 14:10     ` bug#66723: " Hilton Chain via Guix-patches via
2023-11-22 12:12 ` [bug#66723] " 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

  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=CX2R5KPSM94S.223IA5MY5FJU2@guix \
    --to=guix-patches@gnu.org \
    --cc=66723@debbugs.gnu.org \
    --cc=mcsinyx@disroot.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).