From: Brett Gilio <brettg@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, info-guix@gnu.org, help-guix@gnu.org
Subject: Re: New info-guix mailing list for important announcements
Date: Mon, 29 Oct 2018 18:06:13 -0500 [thread overview]
Message-ID: <87h8h4pd3u.fsf@posteo.net> (raw)
In-Reply-To: <87woq0z7ct.fsf@gnu.org>
Ludovic Courtès writes:
> Hello Guix!
>
> We have created a new mailing list for announcements: releases, build
> farm news, security advisories, incompatibilities, etc.
>
> https://lists.gnu.org/mailman/listinfo/info-guix
>
> This is going to be low-traffic, with posts by the developers in charge.
>
> Guix users are very much encouraged to subscribe!
>
> Ludo’.
Grazi, Ludo.
--
Brett M. Gilio
Free Software Foundation, Member
https://gnu.org/s/guix | https://emacs.org
next prev parent reply other threads:[~2018-10-29 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 23:00 New info-guix mailing list for important announcements Ludovic Courtès
2018-10-29 23:06 ` Brett Gilio [this message]
2018-10-31 15:25 ` Alex Vong
2018-11-04 22:51 ` 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=87h8h4pd3u.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=info-guix@gnu.org \
--cc=ludo@gnu.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.
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).