From: reed@reedmedia.net
To: Larry McVoy <lm@mcvoy.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] V6 networking & alarm syscall
Date: Sat, 12 Jan 2019 06:04:27 -0600 (CST) [thread overview]
Message-ID: <alpine.NEB.2.21.1901120559110.21728@t1.m.reedmedia.net> (raw)
In-Reply-To: <20190111221853.GB7733@mcvoy.com>
On Fri, 11 Jan 2019, Larry McVoy wrote:
> On Fri, Jan 11, 2019 at 04:08:25PM -0600, reed@reedmedia.net wrote:
> > Can someone tell me about SCCS behaviour when renaming/moving or
> > deleting files?
...
> SCCS didn't know about renames, it was strictly checkin/checkout.
...
> Anyhoo, I digress, that's all BitKeeper, not SCCS. If you have
> the SCCS history somewhere where I can get it I might be able to
> find the file you want. Just point me at (I know I have that
> set somewhere but no idea where they are).
I was surprised that I didn't see the files at the TUHS archives.
I put the SCCS and s. files into
http://reedmedia.net/~reed/tmp/4.1c1-sccs.tar.gz
1.4MB
408 files
I was looking for the early select() code from ~1981. The earliest I
found was kern_descrip.c from 82/07/15. I think the original source file
got deleted or the file was renamed and lost its history (and the
original SCCS s. file was lost).
Thanks
next prev parent reply other threads:[~2019-01-12 12:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 23:12 Paul Ruizendaal
2019-01-11 0:17 ` Clem cole
2019-01-11 15:33 ` ron
2019-01-11 18:45 ` Clem Cole
2019-01-11 19:06 ` David
2019-01-11 22:08 ` reed
2019-01-11 22:18 ` Larry McVoy
2019-01-12 12:04 ` reed [this message]
2019-01-12 17:20 ` Clem Cole
2019-01-12 18:16 ` Eric Allman
2019-01-13 1:16 ` Madeline Autumn-Rose
2019-01-11 22:47 ` Clem Cole
2019-01-11 22:55 ` Eric Allman
2019-01-11 23:32 ` Warner Losh
2019-01-11 23:27 Paul Ruizendaal
2019-01-12 1:24 Noel Chiappa
2019-01-12 1:58 ` Dave Horsfall
2019-01-12 2:33 ` Warner Losh
2019-01-12 4:14 Noel Chiappa
[not found] <mailman.1.1547258402.6716.tuhs@minnie.tuhs.org>
2019-01-12 11:13 ` Paul Ruizendaal
2019-01-13 10:52 Paul Ruizendaal
2019-01-13 15:39 ` Warner Losh
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=alpine.NEB.2.21.1901120559110.21728@t1.m.reedmedia.net \
--to=reed@reedmedia.net \
--cc=lm@mcvoy.com \
--cc=tuhs@minnie.tuhs.org \
/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).