From: Richard Stallman <rms@gnu.org>
Cc: jerome.marant@free.fr, eliz@gnu.org, rlb@defaultvalue.org,
emacs-devel@gnu.org
Subject: Re: [jerome.marant@free.fr: Re: Possible help with stable Emacs releases.]
Date: Thu, 30 Sep 2004 13:37:31 -0400 [thread overview]
Message-ID: <E1CD4rz-0000Md-Af@fencepost.gnu.org> (raw)
In-Reply-To: <m33c0zg5u2.fsf@kfs-l.imdomain.dk> (storm@cua.dk)
We once discussed the idea to use negative Z values for CVS and pretests,
e.g. instead of 21.3.50.NN we would have 21.4.-99.NN for CVS version
and pretests vould be 21.4.-98, 21.4.-97 etc.
One drawback of this idea is that the pretest version numbers are moving
towards a fixed limit of zero, which puts a bound on them. What we
really want is numbers like 21.4.-1/1, 21.4.-1/2, 21.4.-1/3, where
the pretest version numbers form series converging towards zero.
Or perhaps 21.4-1/2, 21.4-1/3, 21.4-1/4, which converge towards 21.4.
- use MAJOR.MINOR where MINOR is only incremented for bugfix releases and
MAJOR is incremented for non-bugfix releases. I.e. the next release would
then be 22.1 and unicode would be 23.1.
That would be a good scheme, I think.
next prev parent reply other threads:[~2004-09-30 17:37 UTC|newest]
Thread overview: 109+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 7:37 [jerome.marant@free.fr: Re: Possible help with stable Emacs releases.] Richard Stallman
2004-09-27 9:40 ` Kim F. Storm
2004-09-27 11:48 ` Jérôme Marant
2004-09-27 13:08 ` Stefan Monnier
2004-09-27 13:24 ` Jérôme Marant
2004-09-27 14:27 ` Stefan Monnier
2004-09-28 9:01 ` Jérôme Marant
2004-09-27 22:55 ` Richard Stallman
2004-09-28 20:57 ` Jérôme Marant
2004-09-27 13:05 ` Stefan Monnier
2004-09-27 13:21 ` Jérôme Marant
2004-09-27 13:47 ` Miles Bader
2004-09-28 12:37 ` Kim F. Storm
2004-09-29 17:46 ` Rob Browning
2004-09-29 18:04 ` Stefan Monnier
2004-09-29 19:29 ` Rob Browning
2004-09-29 20:09 ` Stefan Monnier
2004-09-29 20:22 ` Jérôme Marant
2004-09-30 0:53 ` Luc Teirlinck
2004-09-30 1:25 ` Miles Bader
2004-09-30 15:40 ` Robert J. Chassell
2004-09-30 17:02 ` Rob Browning
2004-09-30 19:32 ` Robert J. Chassell
2004-09-30 1:56 ` Rob Browning
2004-09-30 7:42 ` Jérôme Marant
2004-09-30 9:36 ` Kim F. Storm
2004-09-30 14:11 ` Eli Zaretskii
2004-09-30 14:32 ` Miles Bader
2004-09-30 15:02 ` Stefan Monnier
2004-09-30 15:34 ` Eli Zaretskii
2004-09-30 14:36 ` Jérôme Marant
2004-09-30 15:00 ` Kim F. Storm
2004-09-30 16:33 ` Rob Browning
2004-09-30 17:37 ` Richard Stallman [this message]
2004-09-30 19:39 ` Robert J. Chassell
2004-10-03 1:18 ` Richard Stallman
2004-09-30 20:26 ` Kim F. Storm
2004-09-30 20:36 ` Stefan Monnier
2004-09-30 20:46 ` Jérôme Marant
2004-09-30 21:40 ` Kim F. Storm
2004-09-30 21:33 ` Kim F. Storm
2004-09-30 21:48 ` Stefan Monnier
2004-09-30 21:42 ` Andreas Schwab
2004-09-30 22:16 ` Kim F. Storm
2004-09-30 22:21 ` Stefan Monnier
2004-10-01 16:43 ` Kim F. Storm
2004-10-03 14:32 ` Richard Stallman
2004-09-30 0:09 ` Miles Bader
2004-09-30 14:21 ` Eli Zaretskii
2004-09-30 14:32 ` Jérôme Marant
2004-09-30 15:31 ` Eli Zaretskii
2004-09-30 14:34 ` Miles Bader
2004-09-30 15:37 ` Eli Zaretskii
2004-09-30 15:53 ` Jérôme Marant
2004-09-30 16:06 ` Eli Zaretskii
2004-09-30 17:20 ` Rob Browning
2004-09-30 17:58 ` Eli Zaretskii
2004-09-30 17:42 ` Stefan Monnier
2004-09-30 20:42 ` Jérôme Marant
2004-09-30 21:35 ` Stefan Monnier
2004-10-01 7:22 ` Jérôme Marant
2004-10-01 12:35 ` Stefan
2004-10-01 14:49 ` Jérôme Marant
2004-10-01 16:25 ` Stefan
2004-10-01 20:31 ` Jérôme Marant
2004-10-03 14:33 ` Richard Stallman
2004-10-03 16:20 ` Jérôme Marant
2004-10-03 14:33 ` Richard Stallman
2004-10-01 20:22 ` Eli Zaretskii
2004-09-30 21:36 ` Kim F. Storm
2004-09-30 19:09 ` Jérôme Marant
2004-10-01 20:27 ` Eli Zaretskii
2004-10-01 21:47 ` [jerome.marant@free.fr: Re: Possible help with stable Emacsreleases.] Lennart Borgman
2004-09-30 16:53 ` [jerome.marant@free.fr: Re: Possible help with stable Emacs releases.] Rob Browning
2004-09-30 19:15 ` Robert J. Chassell
2004-09-30 20:26 ` Jérôme Marant
2004-10-03 14:20 ` Robert J. Chassell
2004-10-04 22:40 ` Rob Browning
2004-10-06 5:28 ` Richard Stallman
2004-10-06 9:12 ` Eli Zaretskii
2004-09-30 14:55 ` Kim F. Storm
2004-09-30 15:41 ` Eli Zaretskii
2004-09-30 15:15 ` Rob Browning
2004-09-30 15:48 ` Eli Zaretskii
2004-09-30 15:58 ` Jérôme Marant
2004-09-30 17:31 ` Stefan Monnier
2004-09-30 18:00 ` Eli Zaretskii
2004-09-30 18:33 ` Stefan Monnier
2004-09-30 21:39 ` Andreas Schwab
2004-10-02 20:47 ` Kai Grossjohann
2004-09-30 15:59 ` Richard Stallman
2004-10-01 6:24 ` Francesco Potorti`
2004-10-04 22:58 ` Rob Browning
2004-10-05 8:34 ` Kim F. Storm
2004-10-05 15:01 ` Rob Browning
2004-10-05 16:18 ` Juri Linkov
2004-10-05 16:34 ` Rob Browning
2004-10-05 17:03 ` Stefan Monnier
2004-10-06 8:39 ` Kim F. Storm
2004-10-05 11:26 ` Stefan
2004-10-05 11:40 ` Jérôme Marant
2004-10-06 11:09 ` Nick Roberts
2004-10-06 11:46 ` Jérôme Marant
2004-10-05 14:39 ` Rob Browning
2004-10-05 14:53 ` Stefan Monnier
2004-10-05 15:28 ` Rob Browning
2004-10-05 15:32 ` Rob Browning
2004-10-06 8:07 ` Kim F. Storm
2004-09-27 12:17 ` Kenichi Handa
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=E1CD4rz-0000Md-Af@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jerome.marant@free.fr \
--cc=rlb@defaultvalue.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).