rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Chris Siebenmann <cks>
To: rc
Subject: Re: 'sam' available from research.att.com!
Date: Wed, 18 Nov 1992 13:27:03 -0500	[thread overview]
Message-ID: <92Nov18.132708est.2664@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: byron's message of Wed, 18 Nov 92 13:16:09 -0500. <9211181816.AA10576@netapp.netapp.com>

 Note that the people at Bell Labs who are doing have been silently
updating the sam distribution; unless you've sent them bug reports,
you may not have heard about the new versions. The bug in options
processing that Byron found has been fixed, for example (along with
a bunch of others).

	- cks


  reply	other threads:[~1992-11-18 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-11-18 18:16 Byron Rakitzis
1992-11-18 18:27 ` Chris Siebenmann [this message]
1992-11-18 20:36 ` Byron's comments John Mackin
  -- strict thread matches above, loose matches on Subject: below --
1992-11-18 17:20 'sam' available from research.att.com! Arnold Robbins
1992-11-18 23:29 ` Christopher JS Vance
1992-11-18 17:17 rsalz
1992-11-18 16:31 Arnold Robbins
1992-11-18 17:35 ` 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=92Nov18.132708est.2664@hawkwind.utcs.toronto.edu \
    --to=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).