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

> From: "Marshall, Simon" <simon.marshall@misys.com>
> Date: Fri, 22 Mar 2002 17:34:13 -0000
> 
> After all, if my effort will not make a difference to any user
> (including me) until 21.3 or later, I'm thinking why bother putting
> that effort in for 21.2?

I can think about two reasons:

First, it's possible that the fix _will_ be in the next release.  It
depends on the problem you find and the change needed to fix it.

Second, even if the fix will not be in the next release, reporting the
problem immediately would allow enough time to find a good fix for it,
and to test that fix before the pretest of the next version even
starts (there are quite a few people who use the CVS head version as a
matter of routine).

By contrast, if you postpone a problem whose fix is not a trivial one
until the next pretest, there are chances it won't get into that
pretest as well.

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


  reply	other threads:[~2002-03-22 18:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22 17:34 emacs 21.2 Marshall, Simon
2002-03-22 18:47 ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-22 17:05 Marshall, Simon
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  9:40 Marshall, Simon
2002-03-22 11:44 ` Eli Zaretskii
2002-03-23 16:13 ` Richard Stallman

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-Fri22Mar2002204714+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=lektu@terra.es \
    /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).