unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bug#142608: emacs21: please apply flyspell patch from preview-latex package
Date: Wed, 17 Apr 2002 10:04:53 -0600 (MDT)	[thread overview]
Message-ID: <200204171604.g3HG4ru24873@aztec.santafe.edu> (raw)
In-Reply-To: <x51ydgk3i6.fsf@tupik.goethe.zz> (David.Kastrup@t-online.de)

    fixed for perhaps half a year now (and still has), I would really be
    surprised if the fixes (or their supersession by larger changes taking
    them into account) would not already be present in RC.

Mere passage of time does not put anything into RC.
(How could it?)  That happens only under human control.
That is why I suggested you put these into RC.

      IIRC, 21.3 was
    not supposed to be mere bug fixes as compared to 21.2, was it?

We have decided to base 21.3 on RC.  The release from HEAD
will be 21.4.

    I would first have to get developer access to GNU Emacs, I am
    registered as "dak" at Savannah and have signed all the necessary
    papers.

Eli, can you do that?

  parent reply	other threads:[~2002-04-17 16:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E16wEb6-0005Op-00@volition>
     [not found] ` <871ydiq5ju.fsf@raven.i.defaultvalue.org>
     [not found]   ` <x57kna8th5.fsf@tupik.goethe.zz>
2002-04-15 22:00     ` Bug#142608: emacs21: please apply flyspell patch from preview-latex package Richard Stallman
2002-04-15 22:20       ` David Kastrup
2002-04-16  6:25         ` Eli Zaretskii
2002-04-16 14:00           ` David Kastrup
2002-04-16 17:07             ` Juanma Barranquero
2002-04-16 18:12             ` Eli Zaretskii
2002-04-17 16:04         ` Richard Stallman [this message]
2002-04-17 21:36           ` David Kastrup
2002-04-18 10:20             ` Stefan Monnier
2002-04-19  5:24               ` Richard Stallman
2002-04-19 15:47                 ` Stefan Monnier
2002-04-18 19:22             ` Eli Zaretskii
2002-04-19 18:42               ` Richard Stallman
2002-04-19 19:51                 ` Eli Zaretskii
2002-04-20 19:58               ` David Kastrup

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=200204171604.g3HG4ru24873@aztec.santafe.edu \
    --to=rms@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).