From: David.Kastrup@t-online.de (David Kastrup)
Cc: emacs-devel@gnu.org
Subject: Re: Bug#142608: emacs21: please apply flyspell patch from preview-latex package
Date: 16 Apr 2002 00:20:49 +0200 [thread overview]
Message-ID: <x51ydgk3i6.fsf@tupik.goethe.zz> (raw)
In-Reply-To: <200204152200.g3FM06K23791@aztec.santafe.edu>
Richard Stallman <rms@gnu.org> writes:
> If these bugs are bothering people, let's put the fixes into 21.3.
> Could you check them in to RC?
> 21.3 will be made from RC.
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.
However, since the HEAD branch of Emacs has had those particular bugs
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. IIRC, 21.3 was
not supposed to be mere bug fixes as compared to 21.2, was it?
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Email: David.Kastrup@t-online.de
next prev parent reply other threads:[~2002-04-15 22:20 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 [this message]
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
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=x51ydgk3i6.fsf@tupik.goethe.zz \
--to=david.kastrup@t-online.de \
--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).