From: byron@netapp.com (Byron Rakitzis)
To: raymondc@microsoft.com, rc@hawkwind.utcs.toronto.edu
Subject: Re: changes to rc
Date: Sun, 19 Sep 1993 16:48:19 -0400 [thread overview]
Message-ID: <9309192048.AA29805@netapp.com> (raw)
>ObRC: Hey Byron, how close are we to 1.5?
Well, as long as you are asking "in public" I may as well answer "in
public". The truth is that I simply cannot offer any promises. I have
made too many guesses and subsequent excuses to even hazard something
now. I think I need a few days' worth of concentration, mainly to
"fault in" all the issues that have been discussed over the last year
or so and to reach some conclusions of my own. So far I have been unable
to do this due to the many things keeping me active in my personal and
professional life. The Network Appliance software is close to release
1.1 now, and once the smoke clears I will possibly have some time to
concentrate on rc. Bug me in a few weeks again..
next reply other threads:[~1993-09-19 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-19 20:48 Byron Rakitzis [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-09-19 13:32 raymondc
1993-09-17 19:50 Chris Siebenmann
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=9309192048.AA29805@netapp.com \
--to=byron@netapp.com \
--cc=raymondc@microsoft.com \
--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).