From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 62737-done@debbugs.gnu.org
Subject: bug#62737: [PATCH 0/9] skarnet s6 updates
Date: Mon, 10 Apr 2023 19:15:31 +0800 [thread overview]
Message-ID: <87h6to0yzw.fsf_-_@envs.net> (raw)
In-Reply-To: <ZDMCGjGHpntB00ey@jasmine.lan> (Leo Famulari's message of "Sun, 9 Apr 2023 14:21:14 -0400")
Leo Famulari <leo@famulari.name> writes:
> Thanks! They build for me on x86_64. You could wait for QA, but I think
> it's okay to push now if the updates are working for you.
Pushed, thank you!
prev parent reply other threads:[~2023-04-10 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-09 7:49 [bug#62737] [PATCH 0/9] skarnet s6 updates iyzsong--- via Guix-patches via
2023-04-09 7:52 ` [bug#62737] [PATCH 1/9] gnu: skalibs: Update to 2.13.1.1 iyzsong--- via Guix-patches via
2023-04-09 7:52 ` [bug#62737] [PATCH 2/9] gnu: execline: Update to 2.9.3.0 iyzsong--- via Guix-patches via
2023-04-09 7:52 ` [bug#62737] [PATCH 3/9] gnu: s6: Update to 2.11.3.2 iyzsong--- via Guix-patches via
2023-04-09 7:52 ` [bug#62737] [PATCH 4/9] gnu: s6-dns: Update to 2.3.5.5 iyzsong--- via Guix-patches via
2023-04-09 7:52 ` [bug#62737] [PATCH 5/9] gnu: s6-networking: Update to 2.5.1.3 iyzsong--- via Guix-patches via
2023-04-09 7:52 ` [bug#62737] [PATCH 6/9] gnu: s6-rc: Update to 0.5.4.1 iyzsong--- via Guix-patches via
2023-04-09 7:52 ` [bug#62737] [PATCH 7/9] gnu: s6-portable-utils: Update to 2.3.0.2 iyzsong--- via Guix-patches via
2023-04-09 7:52 ` [bug#62737] [PATCH 8/9] gnu: s6-linux-init: Update to 1.1.1.0 iyzsong--- via Guix-patches via
2023-04-09 7:52 ` [bug#62737] [PATCH 9/9] gnu: s6-linux-utils: Update to 2.6.1.2 iyzsong--- via Guix-patches via
2023-04-09 18:21 ` [bug#62737] [PATCH 0/9] skarnet s6 updates Leo Famulari
2023-04-10 11:15 ` 宋文武 via Guix-patches via [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=87h6to0yzw.fsf_-_@envs.net \
--to=guix-patches@gnu.org \
--cc=62737-done@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=leo@famulari.name \
/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.