From: phillip.lord@russet.org.uk (Phillip Lord)
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: Windows Snapshots
Date: Fri, 01 Dec 2017 19:03:20 +0000 [thread overview]
Message-ID: <87a7z2l18n.fsf@russet.org.uk> (raw)
In-Reply-To: <977a243b-b55d-46d2-bc59-65af975f28d1@default> (Drew Adams's message of "Fri, 1 Dec 2017 10:20:48 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
>> They are all Emacs-27 snapshot code.
>
> Dunno what "Emacs-27 snapshot code" means. A snapshot is
> typicaly something passive: one frame from a time stream.
>
> Presumably you wanted to communicate that they each install
> Emacs reflecting the source code at a given moment in time.
> But that's clear anyway from the dates.
True. I could drop snapshot and leave the name, although "snapshot" is
pretty commonly used to mean "not a proper release".
> Anyway, it was just a suggestion, to help avoid confusion.
> Call them freds, if you like.
I think it's a good idea actually. Gnus used (perhaps still does) to
have funky names for releases -- ding, oort and that sort of
thing. Perhaps, we should be the same for Emacs. "Fred" for Emacs-27,
"Bob" for Emacs-28? Good idea or what?
Phil
next prev parent reply other threads:[~2017-12-01 19:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 15:42 Windows Snapshots Phillip Lord
2017-12-01 16:03 ` Drew Adams
2017-12-01 17:56 ` Phillip Lord
2017-12-01 18:20 ` Drew Adams
2017-12-01 19:03 ` Phillip Lord [this message]
2017-12-01 19:20 ` Drew Adams
2017-12-03 0:07 ` Stefan Monnier
2017-12-04 12:00 ` Phillip Lord
2017-12-04 12:16 ` Nicolas Petton
2017-12-04 14:36 ` Phillip Lord
2017-12-04 15:02 ` Drew Adams
2017-12-04 15:00 ` Drew Adams
2017-12-05 10:22 ` Phillip Lord
2017-12-05 17:22 ` Sivaram Neelakantan
2017-12-09 11:22 ` Phillip Lord
-- strict thread matches above, loose matches on Subject: below --
2019-09-20 14:36 Phillip Lord
2019-10-24 16:36 ` Drew Adams
2019-11-11 17:27 ` Phillip Lord
2019-11-11 17:48 ` Drew Adams
2019-11-11 23:37 ` phillip.lord
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7z2l18n.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=drew.adams@oracle.com \
--cc=emacs-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/emacs.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).