From: Justin Sheehy <justin@linus.mitre.org>
Cc: xemacs-beta@xemacs.org
Subject: Re: Pterodactyl Gnus v0.6 is released
Date: 31 Aug 1998 00:51:22 -0400 [thread overview]
Message-ID: <glm4sutycs5.fsf@caffeine.mitre.org> (raw)
In-Reply-To: SL Baur's message of "30 Aug 1998 04:10:01 -0700"
SL Baur <steve@xemacs.org> writes:
> Heh. O.K. "Naming Czar", please come up with a new name for XEmacs
> that doesn't suck[1] and the developers will accept. Please? Pretty
> please? :-)
Indeed.
Recently, one of the lower-level sysadmins at a place I know was
listing and describing all of the software available in their
distributed-filesystem-mounted software repository.
It took some effort to convince said person that "XEmacs" should not
have a description string of "X Window interface to Emacs".
*sigh*
--
Justin Sheehy
In a cloud bones of steel.
prev parent reply other threads:[~1998-08-31 4:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-29 22:59 Lars Magne Ingebrigtsen
1998-08-30 5:14 ` Jason R Mastaler
1998-08-30 9:57 ` Lars Magne Ingebrigtsen
1998-08-30 6:49 ` Randal Schwartz
1998-08-30 11:10 ` SL Baur
1998-08-31 4:51 ` Justin Sheehy [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=glm4sutycs5.fsf@caffeine.mitre.org \
--to=justin@linus.mitre.org \
--cc=xemacs-beta@xemacs.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 NNTP newsgroup(s).