From: Larry McVoy <lm@mcvoy.com>
To: Dan Cross <crossd@gmail.com>
Cc: Marc Rochkind <mrochkind@gmail.com>,
Mark Seiden <mseiden@gmail.com>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: SCCS roach motel
Date: Fri, 13 Dec 2024 17:39:43 -0800 [thread overview]
Message-ID: <20241214013943.GJ11590@mcvoy.com> (raw)
In-Reply-To: <CAEoi9W4YfRa_0i4wCYqhXXa_ifaCEwZpaN43__SToZw_LMY1nQ@mail.gmail.com>
On Fri, Dec 13, 2024 at 08:27:54PM -0500, Dan Cross wrote:
> On Fri, Dec 13, 2024 at 8:12???PM Marc Rochkind <mrochkind@gmail.com> wrote:
> > On Fri, Dec 13, 2024 at 2:10???PM Dan Cross <crossd@gmail.com> wrote:
> >> I had heard a story once, that based on what you wrote today, I now
> >> think is apocryphal and never actually happened.
> >>
> >> The story was that there was a bug in early SCCS where a source file
> >> had to be checked in twice before it could be (successfully) checked
> >> out. The bug was such that if one only checked it in once and tried to
> >> check it out, it would truncate the file. "Programmers using it just
> >> learned to check in twice."
> >>
> >> I never used SCCS extensively, and certainly never observed that
> >> behavior, so chucked it up to the bug having been long fixed. As I
> >> mentioned above, I doubt it was ever there to begin with. A fun story,
> >> though.
> >
> > This is completely ridiculous. No program I wrote ever had one of those bug things.
>
> Oh dear, I do hope no offense was taken. As I said, I firmly believe
> the story was apocryphal.
>
> The identity of the person from whom I heard it is probably known to
> at least some of the USENIX old school crew; I rather thought at the
> time they were under the impression that SCCS was the result of a
> large team, or perhaps some kind of fork.
>
> Anyway, I don't mean to belabor the point. Please accept my apologies
> if the story rubbed you the wrong way.
I'm 90% sure Marc was joking, I got it.
next prev parent reply other threads:[~2024-12-14 1:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 16:52 [TUHS] " Marc Rochkind
[not found] ` <A6DE3D0A-8ED7-4E82-87CF-F2BC7AE11761@seiden.com>
2024-12-13 17:58 ` [TUHS] " Marc Rochkind
2024-12-13 21:09 ` Dan Cross
2024-12-14 1:11 ` Marc Rochkind
2024-12-14 1:27 ` Dan Cross
2024-12-14 1:39 ` Larry McVoy [this message]
2024-12-14 6:20 ` Marc Rochkind
2024-12-14 1:38 ` Larry McVoy
2024-12-13 18:06 ` Larry McVoy
2024-12-13 18:32 ` Marc Rochkind
2024-12-13 18:39 ` Marc Rochkind
2024-12-13 18:49 ` Larry McVoy
2024-12-13 18:55 ` Larry McVoy
2024-12-13 19:55 ` Henry Bent
2024-12-14 18:29 ` arnold
2024-12-14 18:59 ` Larry McVoy
2024-12-13 21:46 ` Clem Cole
2024-12-13 21:22 ` Rob Pike
2024-12-13 21:27 ` Rob Pike
2024-12-13 21:37 ` Aron Insinga
2024-12-13 21:40 ` Aron Insinga
2024-12-14 0:37 ` Luther Johnson
2024-12-13 22:33 Norman Wilson
2024-12-17 0:21 ` andrew
2024-12-13 22:57 Norman Wilson
2024-12-13 23:19 ` Larry McVoy
2024-12-13 23:38 ` Warner Losh
2024-12-14 0:53 ` Larry McVoy
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=20241214013943.GJ11590@mcvoy.com \
--to=lm@mcvoy.com \
--cc=crossd@gmail.com \
--cc=mrochkind@gmail.com \
--cc=mseiden@gmail.com \
--cc=tuhs@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).