unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: Emacs pretest 22.0.99
Date: Tue, 24 Apr 2007 18:26:39 +1200	[thread overview]
Message-ID: <17965.41759.649245.855776@farnswood.snap.net.nz> (raw)
In-Reply-To: <uy7kiwb9a.fsf@gnu.org>

 > > How about numbering bug fix releases, which presumably could be made
 > > shortly after the main release if necessary, 22.1.1, 22.1.2, ... this
 > > time?
 > 
 > This was discussed at length some time ago, but I believe we didn't
 > decide to change the numbering.

Many schemes were discussed, I can't remember them all but I'm sure you're
right.  Perhaps we could decide now.

 >                                  It cannot be changed without changes
 > elsewhere; e.g., report-emacs-bug knows about the numbering scheme,
 > and so do the files involved in setting the minor version number
 > during the build process.
 >
 > In other words, I think it's too late to change this for Emacs 22.

Well report-emacs-bug just seems to look for three dots:

(string-match "\\..*\\..*\\." "22.0.98.1")
2
(string-match "\\..*\\..*\\." "22.1.1")
nil
(string-match "\\..*\\..*\\." "22.1")
nil

What are the other files?  Do they just test for three dots also?

-- 
Nick                                           http://www.inet.net.nz/~nickrob

  reply	other threads:[~2007-04-24  6:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24  2:51 Emacs pretest 22.0.99 Chong Yidong
2007-04-24  5:48 ` Nick Roberts
2007-04-24  6:13   ` Eli Zaretskii
2007-04-24  6:26     ` Nick Roberts [this message]
2007-04-24 12:10       ` Eli Zaretskii
2007-04-24 22:53         ` Nick Roberts
2007-04-25  3:26           ` Eli Zaretskii
2007-04-25  3:57             ` Nick Roberts
2007-04-25 18:02               ` Eli Zaretskii
2007-04-24 21:35       ` Richard Stallman
2007-04-24 22:57         ` Nick Roberts
2007-04-25 14:52           ` Richard Stallman
2007-04-24  6:27 ` Lennart Borgman (gmail)
2007-04-24  7:40   ` Lennart Borgman (gmail)
2007-04-24  7:59   ` Jason Rumney
2007-04-24  8:16     ` Lennart Borgman (gmail)
2007-04-24  8:29       ` Jason Rumney
2007-04-24  8:35         ` Lennart Borgman (gmail)
2007-04-24  8:44           ` Jason Rumney
2007-04-24 11:05             ` Lennart Borgman (gmail)
2007-04-24  8:03 ` Takashi Hiromatsu
2007-04-24 12:24   ` Eli Zaretskii
2007-04-25  0:41     ` Takashi Hiromatsu
2007-04-27 13:21       ` Eli Zaretskii
2007-05-01  7:08         ` Takashi Hiromatsu
2007-05-04 13:38           ` Eli Zaretskii
2007-04-26 23:17 ` Giorgos Keramidas

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=17965.41759.649245.855776@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --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).