Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!think!ames!oliveb!sun!gorodish!guy
From: guy@gorodish.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: RCS vs. SCCS and make
Message-ID: <20516@sun.uucp>
Date: Fri, 5-Jun-87 18:58:33 EDT
Article-I.D.: sun.20516
Posted: Fri Jun  5 18:58:33 1987
Date-Received: Sat, 6-Jun-87 20:16:07 EDT
References: <41@esosun.UUCP> <20393@sun.uucp> <42@loki.esosun.UUCP>
Sender: news@sun.uucp
Lines: 26

> Fading away means it is available at proportionally fewer sites compared
> to some short time ago.  Dying means it is availabe at fewer sites then
> some short time ago.

What if it's available at more, but proportionally fewer, sites than
some short time ago?  "Fading away" is a loaded term, implying that
it is losing favor; it may just not be *gaining* sufficient favor to
encourage more vendors to adopt it.

> I thought the time to retrieve a version from SCCS was proportional
> to the number of changes since the original version was created.  In
> other words, a lot of versions implies slow retrieve time for SCCS.
> I'd imagine the time to retrieve intermediate versions (i.e. between 1.1
> and the current version) is completely dependant on the number of changes
> between (1.1 for SCCS and current version of RCS) and the desired version.

Nope.  The time to retrieve a version from SCCS is proportional to
the size of the file, and to the number of lines that have been
changed in all the versions checked in, but is independent of the
version being retrieved.  SCCS does not store forward "diff"s; it
stores text lines, and control lines that say "the next batch of
lines first appear in version N", "the next batch of lines disappear
in version M", etc..
	Guy Harris
	{ihnp4, decvax, seismo, decwrl, ...}!sun!guy
	guy@sun.com