From: jgart via Guix-patches via <guix-patches@gnu.org>
To: "Sergey Trofimov" <sarg@sarg.org.ru>
Cc: 63893@debbugs.gnu.org, Zhu Zihao <all_but_last@163.com>
Subject: [bug#63893] [PATCH v3 2/2] gnu: nix: Update to 2.16.1.
Date: Sun, 25 Jun 2023 03:01:00 +0000 [thread overview]
Message-ID: <e407a6f1232efbd7781bb3ad6b24f016@dismail.de> (raw)
In-Reply-To: <878rc8zm77.fsf@sarg.org.ru>
hi Sergey,
Oh funny, ok, thanks for letting me know ;()
next prev parent reply other threads:[~2023-06-25 3:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 16:29 [bug#63893] [PATCH]: gnu: nix: Update to 2.16.0 Zhu Zihao
[not found] ` <handler.63893.B.168589626726853.ack@debbugs.gnu.org>
2023-06-04 16:37 ` [bug#63893] Acknowledgement ([PATCH]: gnu: nix: Update to 2.16.0.) Zhu Zihao
2023-06-04 16:41 ` [bug#63893] [PATCH 1/3] gnu: Add rapidcheck Zhu Zihao
2023-06-04 16:34 ` [bug#63893] [PATCH 3/3] gnu: nix: Use HTTPS for package source Zhu Zihao
2023-06-04 16:43 ` [bug#63893] [PATCH 2/3] gnu: nix: Update to 2.16.0 Zhu Zihao
2023-06-11 14:11 ` [bug#63893] [PATCH v2 1/2] gnu: Add rapidcheck jgart via Guix-patches via
2023-06-11 14:11 ` [bug#63893] [PATCH v2 2/2] gnu: nix: Update to 2.16.1 jgart via Guix-patches via
2023-06-13 9:17 ` Zhu Zihao
2023-06-11 14:29 ` [bug#63893] [PATCH v3 1/2] gnu: Add rapidcheck jgart via Guix-patches via
2023-06-11 14:29 ` [bug#63893] [PATCH v3 2/2] gnu: nix: Update to 2.16.1 jgart via Guix-patches via
2023-06-19 15:47 ` Zhu Zihao
2023-06-24 17:12 ` jgart via Guix-patches via
2023-06-24 17:20 ` jgart via Guix-patches via
2023-06-24 19:34 ` Sergey Trofimov
2023-06-25 3:01 ` jgart via Guix-patches via [this message]
2023-06-26 21:41 ` [bug#63893] " jgart via Guix-patches via
2023-06-26 22:16 ` Sergei Trofimovich
2023-06-27 6:03 ` jgart via Guix-patches via
2023-06-27 7:05 ` Sergei Trofimovich
2023-07-12 4:00 ` bug#63893: [PATCH v3 2/2] " jgart via Guix-patches via
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=e407a6f1232efbd7781bb3ad6b24f016@dismail.de \
--to=guix-patches@gnu.org \
--cc=63893@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=jgart@dismail.de \
--cc=sarg@sarg.org.ru \
/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).