From: Tom Culliton <culliton@clark.net>
To: alan@oldp.nmsu.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re: RC => POSIX
Date: Thu, 6 Mar 1997 12:40:01 -0500 [thread overview]
Message-ID: <199703061740.MAA17601@clark.net> (raw)
> The behaviour of rc is, for all intents and purposes, fixed. We are
Agreed... More or less... We never did get an official version with
read in it as Byron discussed once.
> talking about rc-1.5 not because we want new features or want bugs
> fixed,
Even if we don't add new features I'd sure like to see bugs fixed! And
yes, there are bugs, software without bugs is even rarer than being
alive and not having dirty laundry. I'd like to see a 1.5 with the
known good fixes incorporated before we start talking about any major
rewrites. Personally I plan to do my part by running rc through every
static and dynamic checker available to me, and posting fixes for
anything that turns up.
> but because we want rc-1.4 to work on new iron. Presumably,
> those people with old iron can continue to run rc-1.4.
This was exactly what I was arguing against!
Tom
next reply other threads:[~1997-03-06 17:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-06 17:40 Tom Culliton [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-03-29 20:23 Bengt Kleberg
1997-03-27 9:58 Malte Uhl
1997-03-26 11:54 Byron Rakitzis
1997-03-26 16:45 ` Greg A. Woods
1997-03-26 8:33 Bengt Kleberg
1997-03-26 16:38 ` Greg A. Woods
1997-03-25 22:30 Byron Rakitzis
1997-03-24 9:18 Bengt Kleberg
1997-03-24 20:22 ` Greg A. Woods
1997-03-08 0:13 Byron Rakitzis
1997-03-06 17:15 Alan Watson
1997-03-06 17:54 ` Scott Schwartz
[not found] <199703061512.KAA21040@explorer2.clark.net>
1997-03-06 16:57 ` Malte Uhl
1997-03-06 16:54 Tom Culliton
1997-03-06 15:22 Tom Culliton
1997-03-06 14:09 Bengt Kleberg
1997-03-06 13:46 Tom Culliton
1997-03-06 10:16 Bengt Kleberg
1997-03-07 1:45 ` Greg A. Woods
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=199703061740.MAA17601@clark.net \
--to=culliton@clark.net \
--cc=alan@oldp.nmsu.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).