unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: emacs 21.2
Date: Fri, 22 Mar 2002 13:44:56 +0200	[thread overview]
Message-ID: <6480-Fri22Mar2002134455+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <FC3DA3DC8D4AD311AB910020352A8FDC0BC62C7D@eagle.midas-kapiti.com> (simon.marshall@misys.com)

> From: "Marshall, Simon" <simon.marshall@misys.com>
> Date: Fri, 22 Mar 2002 09:40:59 -0000
> 
> I realise that Emacs releases have changed, and odd-numbered releases
> are different in some way to even-numbered releases, but could someone
> explain what the difference is meant to be?

There's no such rule; odd-numbered releases are not special.

What actually happens is that the bug-fix releases, such as 21.2, are
produced from a CVS branch, while development continues on the trunk.
Changes committed on the trunk alone won't be seen in the releases
produced from the branch.  If we decide that there should be another
bugfix release, it will be labeled 21.3, but will still be produced
from the release branch.

This didn't start with Emacs 21, btw: Emacs 20.6 and 20.7 were also
produced from a branch (except that in that case, ``the branch'' was
a separate directory rather than a VC branch).

> Many of the problems I raised since the last pretest (AFAIK 21.1.90,
> almost 2 months ago), which (AFAIK) were fixed when reported, are not
> fixed in 21.2.

As a matter of principle, the release branch only gets safe bugfixes,
so it's possible that some of the changes are not there if they were
deemed unsafe, or if the bugs were deemed not grave enough to risk a
change.  It is also possible that we forgot to commit the changes to
the branch, so please tell what changes, specifically, do you have in
mind.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-03-22 11:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22  9:40 emacs 21.2 Marshall, Simon
2002-03-22 11:44 ` Eli Zaretskii [this message]
2002-03-23 16:13 ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2002-03-22 12:43 Marshall, Simon
2002-03-22 14:21 ` Eli Zaretskii
2002-03-22 15:20   ` Marshall, Simon
2002-03-22 16:36     ` Juanma Barranquero
2002-03-22 17:45     ` Eli Zaretskii
2002-03-22 19:38     ` Jason Rumney
2002-03-22 23:54     ` Miles Bader
2002-03-23  8:59       ` Eli Zaretskii
2002-03-23 16:15     ` Richard Stallman
2002-03-23  9:03   ` Per Abrahamsen
2002-03-23 10:12     ` Eli Zaretskii
2002-03-24 15:51     ` Richard Stallman
2002-03-24 18:04       ` Eli Zaretskii
2002-03-25 12:02         ` Richard Stallman
2002-03-25 19:45           ` Eli Zaretskii
2002-03-26 10:14             ` Werner LEMBERG
2002-03-28  4:55               ` Richard Stallman
2002-03-28  9:37                 ` Eli Zaretskii
2002-03-29 17:15                   ` Florian Weimer
2002-03-29 17:32                     ` Eli Zaretskii
2002-03-29 17:47                       ` Florian Weimer
2002-03-22 16:52 ` Stefan Monnier
2002-03-22 17:05 Marshall, Simon
2002-03-22 17:34 Marshall, Simon
2002-03-22 18:47 ` Eli Zaretskii

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=6480-Fri22Mar2002134455+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --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).