rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: byron@ghoti.netapp.com (Byron Rakitzis)
To: culliton@srg.af.mil, rc@hawkwind.utcs.toronto.edu
Subject: Re:  Raising the flag
Date: Wed, 8 Dec 1993 01:12:11 -0500	[thread overview]
Message-ID: <9312080612.AA00991@ghoti.netapp.com> (raw)

Hello again. Code freeze for NAC v1.1 ("FASware") is tomorrow, so I
anticipate some gear changing in the next day or two. Thanks for
reminding me; I haven't forgotten, I just need to schedule some time
where I can fault all of rc back into my head and work on fixing all
the nitty gritty problems.

Part of my reluctance to work on rc-1.5 stems from precisely what Tom
mentions: the fact that 1.4 is working so well. The old "if it ain't
broke" principle.

To this end I have also felt compelled to release something completely
polished, and this has acted as an inhibitor on my actions.

However, I do realize that there some valuable fixes which need to get
out there, and I will do my best at getting them out soon. If that
doesn't happen then I will try to be more realistic about what I can
actually accomplish with my time --- i.e., maybe I will try to solicit
someone's help as Tom suggested.

I thought I'd raise this since I would like to have a reasonable beta
period for any changes, given that there is no way that I as an
individual can test rc in the way that it will surely be stressed when
released to hundreds of users on n different OSes.


             reply	other threads:[~1993-12-08  6:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-12-08  6:12 Byron Rakitzis [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-12-08  1:45 Tom Culliton x2278

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9312080612.AA00991@ghoti.netapp.com \
    --to=byron@ghoti.netapp.com \
    --cc=culliton@srg.af.mil \
    --cc=rc@hawkwind.utcs.toronto.edu \


* 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).