unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David.Kastrup@t-online.de (David Kastrup)
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Bug#142608: emacs21: please apply flyspell patch from preview-latex package
Date: 16 Apr 2002 16:00:11 +0200	[thread overview]
Message-ID: <x5bscjg2vo.fsf@tupik.goethe.zz> (raw)
In-Reply-To: <Pine.SUN.3.91.1020416092148.14169G-100000@is>

Eli Zaretskii <eliz@is.elta.co.il> writes:

> On 16 Apr 2002, David Kastrup wrote:
> 
> > 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.
> 
> I can set you up for write access to the CVS tree, if you want.
> 
> > 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.
> 
> RC got only safe fixes for grave bugs, so it's possible that it doesn't 
> have those changes.  Can you check and say for sure?  (You don't need 
> write access for this; anon CVS will do.)
> 
> > IIRC, 21.3 was
> > not supposed to be mere bug fixes as compared to 21.2, was it?
> 
> Originally, yes; but we've changed our minds, since 21.2 has a small 
> number of annoying bugs, some of them cause crashes and similar nuisance.
> 
> So now it is planned to make 21.3 out of the RC branch.

Where is it?  When looking via the Web interface at the repository, I
only find the branches

patches_21_0
gerd_int
gerd_defvaralias
gerd_dbe
gerd_big
fx-branch
EMACS_21_1_RC
emacs-unicode

- Non-branch tags -

raeburn-tag-7-for-export
raeburn-tag-6-for-export
raeburn-tag-4-for-export
patches_21_0_base
MAIN
HEAD
fx-branch-base
EMACS_PRETEST_21_0_99
EMACS_PRETEST_21_0_98
EMACS_PRETEST_21_0_97
EMACS_PRETEST_21_0_96
EMACS_PRETEST_21_0_95
EMACS_PRETEST_21_0_93
EMACS_PRETEST_21_0_92
EMACS_PRETEST_21_0_91
EMACS_PRETEST_21_0_90
EMACS_PRETEST_21_0_106
EMACS_PRETEST_21_0_105
EMACS_PRETEST_21_0_104
EMACS_PRETEST_21_0_103
EMACS_PRETEST_21_0_102
EMACS_PRETEST_21_0_101
EMACS_PRETEST_21_0_100
EMACS_21_1_BASE
EMACS_21_1
EMACS_20_4
EMACS_20_2
emacs-unicode-base


-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Email: David.Kastrup@t-online.de

  reply	other threads:[~2002-04-16 14:00 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 [this message]
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=x5bscjg2vo.fsf@tupik.goethe.zz \
    --to=david.kastrup@t-online.de \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).