From: ludo@gnu.org (Ludovic Courtès)
To: Jason Self <jason@bluehome.net>
Cc: bug-guix@gnu.org
Subject: Re: Distro name
Date: Thu, 03 Jan 2013 00:32:02 +0100 [thread overview]
Message-ID: <87ehi36u19.fsf@gnu.org> (raw)
In-Reply-To: <1357167116.1974@bluehome.net> (Jason Self's message of "Wed, 02 Jan 2013 14:51:56 -0800 (PST)")
"Jason Self" <jason@bluehome.net> skribis:
> Hmm. It might make sense to differentiate when a third party is
> involved, but not when the GNU Project itself is doing it.
[...]
> I guess it depends on what you define an "an official complete GNU
> system release" to be. That would ultimately have to come from RMS,
> of course, but if the only difference is the kernel (but both kernels
> are official GNU packages) and the distro offered the option of using
> both of them, the line seems perhaps a little bit more blurry in that
> regard.
Hmm yes, that makes sense (and indeed, the longer-term goal is to
support several kernels.)
That would comfort me in choosing the (gnu ...) name space.
Ludo’.
next prev parent reply other threads:[~2013-01-02 23:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 18:02 Distro name Ludovic Courtès
2013-01-02 21:05 ` Jason Self
2013-01-02 21:38 ` Ludovic Courtès
2013-01-02 22:51 ` Jason Self
2013-01-02 23:32 ` Ludovic Courtès [this message]
2013-01-02 21:49 ` Dmitri Paduchikh
2013-01-02 23:14 ` Jason Self
2013-01-02 21:33 ` Dmitri Paduchikh
2013-01-02 21:42 ` Ludovic Courtès
2013-01-03 1:22 ` Nikita Karetnikov
2013-01-02 22:42 ` Andreas Enge
2013-01-02 22:48 ` Ludovic Courtès
2013-01-02 23:09 ` Dmitri Paduchikh
2013-01-03 8:45 ` Andreas Enge
2013-01-03 14:37 ` Ludovic Courtès
2013-01-03 16:42 ` Andreas Enge
2013-01-03 1:12 ` Nikita Karetnikov
2013-01-15 21:36 ` Ludovic Courtès
2013-01-16 8:38 ` Andreas Enge
2013-01-16 16:56 ` Ludovic Courtès
2013-01-17 15:02 ` Andreas Enge
2013-01-18 1:28 ` 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=87ehi36u19.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=jason@bluehome.net \
/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).