From: "Ludovic Courtès" <ludo@gnu.org>
To: L p R n d n <guix@lprndn.info>
Cc: guix-devel@gnu.org
Subject: Re: Communication and Design at Guix
Date: Tue, 15 Jan 2019 23:31:52 +0100 [thread overview]
Message-ID: <87lg3lwo13.fsf@gnu.org> (raw)
In-Reply-To: <cuctvib1f33.fsf@lprndn.info> (L. p. R. n. d. n.'s message of "Mon, 14 Jan 2019 15:36:16 +0100")
L p R n d n <guix@lprndn.info> skribis:
>> The idea is more to have a single “brand”: Guix. Then “Guix System”
>> would be a component of Guix, so to speak, similar to GNOME and its
>> applications.
>
> Ok, I understand. Just thought about something really quick. Do you
> think describing "Guix Sytem" as a system manager, in opposition to
> package manager, would be meaningful?
In theory yes, but in practice “system manager” is terribly vague and
could mean anything, so I’d rather avoid it.
Ludo’.
next prev parent reply other threads:[~2019-01-15 22:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 16:49 Communication and Design at Guix L p R n d n
2019-01-08 17:37 ` Ludovic Courtès
2019-01-09 6:11 ` swedebugia
2019-01-09 21:45 ` Ludovic Courtès
2019-01-10 12:09 ` L p R n d n
2019-01-10 13:20 ` swedebugia
2019-01-10 14:34 ` Ricardo Wurmus
2019-01-13 21:45 ` Ludovic Courtès
2019-01-14 15:02 ` L p R n d n
2019-01-15 10:36 ` zimoun
2019-01-15 18:03 ` nly
2019-01-15 22:08 ` Ricardo Wurmus
2019-01-16 11:00 ` Giovanni Biscuolo
2019-01-15 22:28 ` Ludovic Courtès
2019-01-14 23:25 ` swedebugia
2019-01-15 13:56 ` Ricardo Wurmus
2019-01-15 17:39 ` Julien Lepiller
2019-01-15 22:30 ` Ludovic Courtès
2019-01-10 12:17 ` L p R n d n
2019-01-10 12:57 ` L p R n d n
2019-01-10 14:30 ` Ricardo Wurmus
2019-01-13 21:50 ` Ludovic Courtès
2019-01-14 14:36 ` L p R n d n
2019-01-15 22:31 ` Ludovic Courtès [this message]
2019-01-16 16:31 ` George Clemmer
2019-01-17 0:10 ` swedebugia
2019-01-17 10:58 ` L p R n d n
2019-01-17 11:10 ` Ricardo Wurmus
2019-01-17 14:08 ` swedebugia
2019-01-17 16:24 ` L p R n d n
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=87lg3lwo13.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=guix@lprndn.info \
/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).