<div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif">According to the Unix room fortunes file, the actual quote is</div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div>SCCS: the source-code motel -- your code checks in but it never checks out.<div>Ken Thompson</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sat, Dec 14, 2024 at 3:52 AM Marc Rochkind <<a href="mailto:mrochkind@gmail.com">mrochkind@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>IEEE Transactions on Software Engineering has asked me to write a retrospective on the influence of SCCS over the last 50 years, as my SCCS paper was published in 1975. They consider it one of the most influential papers from TSE's first decade.</div><div><br></div><div>There's a funny quote from Ken Thompson that circulates from time-to-time:</div><div><br></div><div>"SCCS, the source motel! Programs check in and never check out!"</div><div><br></div><div>But nobody seems to know what it means exactly. As part of my research, I asked Ken what the quote meant, sunce I wanted to include it. He explained that it refers to SCCS storing binary data in its repository file, preventing UNIX text tools from operating on the file.</div><div><br></div><div>Of course, this is only one of SCCS's many weaknesses. If you have anything funny about any of the others, post it here. I already have all the boring usual stuff (e.g., long-term locks, file-oriented, no merging).</div><div><br></div><div>Marc Rochkind</div><div><a href="http://mrochkind.com" target="_blank">mrochkind.com</a></div><div><br></div><div><br></div><div><br></div><div><br></div></div>
</blockquote></div>