From: Ahmed Khanzada <me@enzu.ru>
To: zimoun <zimon.toutoune@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>,
info-guix@gnu.org, guix-devel@gnu.org, help-guix@gnu.org,
paren@disroot.org
Subject: Re: GNU Guix 1.4.0rc1 available for testing!
Date: Sat, 03 Dec 2022 09:18:25 -0500 [thread overview]
Message-ID: <87mt84vadq.fsf@enzu.ru> (raw)
In-Reply-To: <86k0383jeq.fsf@gmail.com>
Thank you, Paren and Simon. That was easy. :)
I am now on a seemingly stable Guix 1.4 and GNU/Linux kernel 6.
I'll look into submitting a pull request to the documentation in the
spot where I had expected to find this information.
next prev parent reply other threads:[~2022-12-03 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 9:17 GNU Guix 1.4.0rc1 available for testing! Ludovic Courtès
2022-12-01 15:38 ` Luis Felipe
2022-12-01 21:40 ` Luis Felipe
2022-12-01 22:55 ` Svante Signell
2022-12-03 22:46 ` pelzflorian (Florian Pelz)
2022-12-02 22:17 ` Ahmed Khanzada
2022-12-02 23:10 ` (
2022-12-03 9:50 ` zimoun
2022-12-03 14:18 ` Ahmed Khanzada [this message]
2022-12-03 16:25 ` Kaelyn
2022-12-04 15:50 ` Ahmed Khanzada via Development of GNU Guix and the GNU System distribution.
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=87mt84vadq.fsf@enzu.ru \
--to=me@enzu.ru \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=info-guix@gnu.org \
--cc=ludo@gnu.org \
--cc=paren@disroot.org \
--cc=zimon.toutoune@gmail.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.
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).