Talk:Source Code Control System

From Wikipedia, the free encyclopedia

Contents

[edit] WP:RM

Done. Lachatdelarue (talk) 22:17, 28 Apr 2005 (UTC)

[edit] Rochkind web log links

Why were my links to Marc Rochkind's web log deleted? The note says they are "vanity links", but the log entry discusses Marc's recollections of creating SCCS. I think they are relevant to this article and I would like to see them included. —The preceding unsigned comment was added by Seitz (talk • contribs) .

I'm sorry that I forgot to sign my previous comment.
Is there some way to include the link in question in this article? I found them useful to learning about SCCS, and I think others would, too. Should I put it under "External Links"? Seitz 19:27, 19 February 2006 (UTC)

[edit] Single UNIX Specification

I removed the final paragraph of the main article which discussed the inclusion of SCCS in the Single UNIX Specification. I did so for two reasons:

  • The second paragraph already mentions that SCCS is included in the Single UNIX Specification.
  • The removed paragraph included unattributed opinions.

[edit] Windows based GUI for SCCS

Hi.. Anyone knows if there is a freeware or shareware which provides a windows based GUI for SCCS repositories?

Prasad RA HCL Technologies Bangalore

[edit] Who uses SCCS format

ClearCase, PVCS, and Visual SourceSafe were recently added as systems using the SCCS file format. This was the first I'd heard of that. Does someone have a source to verify this? -- Seitz 04:06, 5 June 2006 (UTC)

-- ClearCase uses an interleaving branching structure like SCCS, but it doesn't use SCCS format, and for very good reason: SCCS only supports a single branch off of the trunk. You can't have a branch off of a branch. (You can, but SCCS's file format doesn't directly support it). The interleaving branch method used by SCCS has an advantage over RCS's format in that it can pull up almost any version just as quickly while RCS's format can pull up the latest version very quickly, but takes longer and longer the more versions it has to go back.

I suspect that PVCS might use SCCS format because it was originally a front end for SCCS. Sablime (another AT&T product) does use SCCS format.

Addendum: I just confirmed that ClearCase definitely does not use SCCS format. I've also found the script pcvs_to_rcs script which is different from the sccs2rcs script that comes with CVS. This pretty much confirms that PCVS doesn't use SCCS format.

I can't vouch for SourceSafe (although I have my doubts since it uses a proprietary database to store its source code) and TeamWare. It is pretty much well known that Bitkeeper uses SCCS format. I'll also add Sublime.

I removed ClearCase and PVCS from the list of version control systems that use SCCS format:

David W.

Since no one was able to document SourceSafe's use of SCCS, I removed it. My comment mistakenly said TeamWare, but I meant SourceSafe.
I also checked the Sablime web site, and found it supports SCCS as an option, but primarily uses SBCS. See:
I can confirm TeamWare definitely uses SCCS. -- Seitz 18:54, 1 October 2006 (UTC)
Retrieved from "http://en.wikipedia.org../../../s/o/u/Talk%7ESource_Code_Control_System_da2f.html"