From: "Ludovic Courtès" <ludo@gnu.org>
To: Zhu Zihao <all_but_last@163.com>
Cc: 59681-done@debbugs.gnu.org
Subject: bug#59681: [PATCH 1/2] gnu: loko: Use G-expressions.
Date: Fri, 02 Dec 2022 23:08:21 +0100 [thread overview]
Message-ID: <87ilitpiga.fsf_-_@gnu.org> (raw)
In-Reply-To: <86edtlrczz.fsf@163.com> (Zhu Zihao's message of "Tue, 29 Nov 2022 23:30:37 +0800")
Hi,
Zhu Zihao <all_but_last@163.com> skribis:
>>From 0d85f05069ccb1bfa648def38375b981893e3601 Mon Sep 17 00:00:00 2001
> From: Zhu Zihao <all_but_last@163.com>
> Date: Tue, 29 Nov 2022 18:59:24 +0800
> Subject: [PATCH 1/2] gnu: loko-scheme: Use G-expressions.
>
> * gnu/packages/loko.scm (loko-scheme)[arguments]: Use G-expressions.
> <#:phases>: In 'akku-fixes', replace "(assoc-ref inputs name)" with
> "this-package-native-input".
> [native-inputs]: Use label-less style.
[...]
>>From 907766669a0efdb16631361ee3f225da8a6767f1 Mon Sep 17 00:00:00 2001
> From: Zhu Zihao <all_but_last@163.com>
> Date: Tue, 29 Nov 2022 19:27:05 +0800
> Subject: [PATCH 2/2] gnu: loko-scheme: Update to 0.12.0.
>
> * gnu/packages/loko.scm (loko-scheme): Update to 0.12.0.
> [arguments]<#:make-flags>: No need to specify GDB scripts directory.
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2022-12-02 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 15:21 [bug#59681] [PATCH 1/2] gnu: loko: Use G-expressions Zhu Zihao
2022-11-29 15:21 ` [bug#59682] [PATCH 2/2] gnu: loko-scheme: Update to 0.12.0 Zhu Zihao
[not found] ` <handler.59682.B.166973533513791.ack@debbugs.gnu.org>
2022-11-29 15:29 ` [bug#59682] Acknowledgement ([PATCH 2/2] gnu: loko-scheme: Update to 0.12.0.) Zhu Zihao
[not found] ` <handler.59681.B.166973532513778.ack@debbugs.gnu.org>
2022-11-29 15:30 ` [bug#59681] Acknowledgement ([PATCH 1/2] gnu: loko: Use G-expressions.) Zhu Zihao
2022-12-02 22:08 ` Ludovic Courtès [this message]
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=87ilitpiga.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=59681-done@debbugs.gnu.org \
--cc=all_but_last@163.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.