unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: dmd’s new name
Date: Thu, 07 Jan 2016 22:02:34 +0100	[thread overview]
Message-ID: <87twmpnlw5.fsf_-_@gnu.org> (raw)
In-Reply-To: <877fufk02r.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 17 Mar 2015 18:25:48 +0100")

ludo@gnu.org (Ludovic Courtès) skribis:

> Walter Bright <walter@digitalmars.com> skribis:
>
>> The D programming language compiler has been called dmd since about
>> 2000 or so. In order to avoid confusion, may I request that the Gnu
>> dmd ("Daemons-managing Daemon") change its acronym?
>
> For the record, GNU’s dmd has been around since ~2003¹.
>
> Changing names is obviously an annoyance, technically and otherwise.
> We’re not opposed to the idea, but that would take a bit more discussion
> among developers.

You might remember this discussion from March 2015.

  https://lists.gnu.org/archive/html/guix-devel/2015-03/msg00176.html

I proposed to Richard Stallman that we change the name to “GNU Shepherd”
and recently got the green light.

Rationale:

  1. A shepherd looks after sheep (or gnus ;-)), and GNU dmd looks after
     daemons.

  2. “Shepherd” ends with a ‘d’, which makes it a good name for a daemon.

  3. It’s a pun in the same spirit as “GNU Hurd”.

  4. We might even rename ‘deco’ to ‘herd’ because it’s the very command
     that allows users to herd their daemons.

Hope you like it.  :-)

Ludo’.

  parent reply	other threads:[~2016-01-07 21:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 22:07 dmd D Programming Language compiler Walter Bright
2015-03-17 17:25 ` Ludovic Courtès
2015-03-17 18:58   ` Walter Bright
2016-01-28 10:37     ` Ludovic Courtès
2016-01-29  2:22       ` Walter Bright
2016-01-07 21:02   ` Ludovic Courtès [this message]
2016-01-07 20:35     ` Re:dmd’s new name d.4.n.1
2016-01-07 21:09     ` dmd’s " Florian Paul Schmidt
2016-01-08  4:21     ` Ricardo Wurmus
2016-01-08  9:06     ` Adam Pribyl
2016-01-08 10:33       ` Ludovic Courtès
2016-01-16 14:22     ` 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=87twmpnlw5.fsf_-_@gnu.org \
    --to=ludo@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).