From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <ericbavier@openmailbox.org>
Cc: guix-devel@gnu.org,
guix-devel-bounces+ericbavier=openmailbox.org@gnu.org
Subject: Re: Create help-guix@gnu.org?
Date: Mon, 21 Dec 2015 22:53:44 +0100 [thread overview]
Message-ID: <87a8p3h3iv.fsf@gnu.org> (raw)
In-Reply-To: <46d68bfc743849f7a98a6631e74b35e9@openmailbox.org> (Eric Bavier's message of "Mon, 21 Dec 2015 17:21:09 +0100")
Eric Bavier <ericbavier@openmailbox.org> skribis:
> On 2015-12-21 16:55, Florian Paul Schmidt wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> On 21.12.2015 14:45, Ludovic Courtès wrote:
>>> Hello!
>>>
>>> Should we create a help-guix@gnu.org mailing list specifically to
>>> answer user questions?
>>
>> Consistent naming schemes are important. I object. How about
>>
>> guix-help@gnu.org
>
> I would agree with this, but we already have bug-guix@gnu.org.
>
> Ludo, are email list names in any GNU guidelines?
Yes, {help,bug,info}-FOO@gnu.org is standard and we cannot change it.
Ludo’.
next prev parent reply other threads:[~2015-12-21 21:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 13:45 Create help-guix@gnu.org? Ludovic Courtès
2015-12-21 14:04 ` Thompson, David
2015-12-21 14:07 ` Daniel Pimentel
2015-12-21 14:19 ` Ricardo Wurmus
2015-12-21 15:21 ` Mark H Weaver
2015-12-21 15:55 ` Florian Paul Schmidt
2015-12-21 16:21 ` Eric Bavier
2015-12-21 17:02 ` Florian Paul Schmidt
2015-12-21 23:45 ` Mathieu Lirzin
2015-12-22 16:46 ` Ludovic Courtès
2015-12-21 21:53 ` Ludovic Courtès [this message]
2015-12-21 17:32 ` Cyril Roelandt
2015-12-21 17:45 ` Christopher Allan Webber
2015-12-21 18:19 ` Leo Famulari
2015-12-21 21:57 ` Ludovic Courtès
2015-12-21 22:24 ` Mark H Weaver
2015-12-22 16:47 ` Ludovic Courtès
2015-12-29 10:44 ` Alex Kost
2015-12-21 22:46 ` anonymiss
2015-12-22 18:39 ` Ludovic Courtès
2015-12-23 9:30 ` Andreas Enge
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=87a8p3h3iv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ericbavier@openmailbox.org \
--cc=guix-devel-bounces+ericbavier=openmailbox.org@gnu.org \
--cc=guix-devel@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.
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).