From: David Kastrup <dak@gnu.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: Nick Roberts <nickrob@snap.net.nz>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: pretest 22.0.100
Date: Thu, 17 May 2007 15:34:42 +0200 [thread overview]
Message-ID: <85hcqby3nx.fsf@lola.goethe.zz> (raw)
In-Reply-To: <464C57DE.2020906@gnu.org> (Jason Rumney's message of "Thu\, 17 May 2007 14\:25\:50 +0100")
Jason Rumney <jasonr@gnu.org> writes:
> David Kastrup wrote:
>> Jason Rumney <jasonr@gnu.org> writes:
>>
>>
>>> Stefan Monnier wrote:
>>>
>>>> Yes, the same mistake was made then (but was not made for Emacs-20.1).
>>>> It's no excuse to repeat it.
>>>>
>>> If it was deliberate, then it was not a mistake. And history shows
>>> that Emacs has always had version numbers, not version strings.
>>>
>>
>> Does not change that people looking for a tarball to download will
>> take a look at the bottom for the most recent one
>
> That is solved by having an emacs-pretest-latest.tar.gz symbolic link
> in the download directory and advising users to use that.
>
> After 18.9 came 18.10, likewise with 19.9 and 19.10. There is no good
> reason to change the rules only for pretests.
Actually, my personal favorite for the next number would be 22.1.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-05-17 13:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 16:47 We can use python.el Richard Stallman
2007-05-12 17:52 ` Chong Yidong
2007-05-12 18:17 ` Juanma Barranquero
2007-05-12 23:03 ` Chong Yidong
2007-05-12 23:36 ` Juanma Barranquero
2007-05-12 23:54 ` Chong Yidong
2007-05-13 1:38 ` Glenn Morris
2007-05-14 8:08 ` Richard Stallman
2007-05-14 8:43 ` Jason Rumney
2007-05-14 14:55 ` Chong Yidong
2007-05-14 17:45 ` Glenn Morris
2007-05-14 18:05 ` Henrik Enberg
2007-05-15 9:47 ` Richard Stallman
2007-05-15 14:11 ` Chong Yidong
2007-05-16 1:39 ` Richard Stallman
2007-05-16 2:51 ` Chong Yidong
2007-05-16 6:02 ` Jan Djärv
2007-05-13 10:33 ` Jason Rumney
2007-05-14 8:09 ` Richard Stallman
2007-05-12 19:02 ` pretest 22.0.100 (was: We can use python.el) Reiner Steib
2007-05-12 22:51 ` pretest 22.0.100 Chong Yidong
2007-05-14 17:01 ` Stefan Monnier
2007-05-14 19:11 ` Juanma Barranquero
2007-05-14 21:26 ` Nick Roberts
2007-05-16 15:48 ` Stefan Monnier
2007-05-17 12:42 ` Andreas Schwab
2007-05-17 12:49 ` Jason Rumney
2007-05-17 13:15 ` David Kastrup
2007-05-17 13:25 ` Jason Rumney
2007-05-17 13:34 ` David Kastrup [this message]
2007-05-17 13:45 ` Ralf Angeli
2007-05-17 13:57 ` Ulrich Mueller
2007-05-17 14:02 ` Alfred M. Szmidt
2007-05-17 13:39 ` Jay Belanger
2007-05-17 14:20 ` Stefan Monnier
2007-05-17 14:32 ` Juanma Barranquero
2007-05-17 16:43 ` Another pretest after 22.0.99 (was: pretest 22.0.100) Reiner Steib
2007-05-13 1:27 ` We can use python.el Michaël Cadilhac
2007-05-14 8:08 ` Richard Stallman
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=85hcqby3nx.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nickrob@snap.net.nz \
/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).