From: Tom Culliton <culliton@clark.net>
To: Tim Goodwin <tgoodwin@cygnus.co.uk>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: Development snapshots now available
Date: Tue, 21 Jul 1998 14:48:00 -0400 [thread overview]
Message-ID: <199807211848.OAA16191@shell.clark.net> (raw)
In-Reply-To: Your message of "Tue, 21 Jul 1998 12:17:08 EDT." <KlYAABm/tDWJsgQA@nan.cygnus.co.uk>
On Tue, 21 Jul 1998 12:17:08 EDT, Tim Goodwin wrote:
> The perceived problem that I'm trying to solve is this. It's a long
> time since I released rc-1.5b2. A number of problems, some of them
> serious, have come to light since that release and been fixed. However,
> I'm not ready to make another beta release yet.
The last 1.5b3 we were batting around looked pretty good to me. So
good that I even installed it as my standard version for everyday use.
What kind of outstanding issues are left? I'll be more than happy to
lend an extra eye on any remaining soft spots.
> Any thoughts, comments, or suggestions are most welcome.
;-) How about, "Keep up the good work!" Seriously 1.5b3 is looking
great from where I sit.
Tom
prev parent reply other threads:[~1998-07-21 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-21 16:17 Tim Goodwin
1998-07-21 18:48 ` Tom Culliton [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199807211848.OAA16191@shell.clark.net \
--to=culliton@clark.net \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=tgoodwin@cygnus.co.uk \
/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.
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 NNTP newsgroup(s).