From: "Marshall, Simon" <simon.marshall@misys.com>
Cc: emacs-devel@gnu.org
Subject: RE: emacs 21.2
Date: Fri, 22 Mar 2002 17:34:13 -0000 [thread overview]
Message-ID: <FC3DA3DC8D4AD311AB910020352A8FDC0BC62C86@eagle.midas-kapiti.com> (raw)
> If I understand you right, you're saying that you consider pretesting
> valuable for you if it is going to help to solve ASAP the problems you
> encounter/suffer.
Not quite. Pretesting is worthwhile (for me)
right-now-this-moment-as-I-speak if the effort I put in will result in
fixes in the next release. If the effort will not result in fixes, I
would be tempted to put it off until I think it will. 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? It
won't make any difference to anyone and it's not like I have time to
burn.
So, I thought my effort would be worthwhile for 21.2, but it turns out I
was wasting my time and I could've left it "until later" without it
making any difference to Emacs for users (and pretesters if not
developers). Mañana.
The other point---"ASAP". I don't care if I don't get patches for fixes
to a pretest, though I'm happy to test them. I don't care if the next
release with the fixes is not soon----I wouldn't be a pretester if that
was the case.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2002-03-22 17:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 17:34 Marshall, Simon [this message]
2002-03-22 18:47 ` emacs 21.2 Eli Zaretskii
-- 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=FC3DA3DC8D4AD311AB910020352A8FDC0BC62C86@eagle.midas-kapiti.com \
--to=simon.marshall@misys.com \
--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).