Path: utzoo!attcan!uunet!unisoft!asa
From: asa@unisoft.UUCP (Asa Romberger)
Newsgroups: comp.unix.questions
Subject: Re: SCCS version control
Message-ID: <1583@unisoft.UUCP>
Date: 13 Dec 88 17:28:20 GMT
References: <3217@ingr.UUCP>
Reply-To: asa@noir.UUCP (Asa Romberger)
Distribution: na
Organization: UniSoft Corporation, Emeryville Ca.
Lines: 18

In article <3217@ingr.UUCP> markv@ingr.UUCP (Mark VandenBrink) writes:
>In developing a product under SCCS, we have, finally, gotten to the point
>where we need to make a release.  So far no problems; however, I would like
>to "remember" or baseline our platform so that some later time (fixes release,
>etc.) I can automagically recreate the platform.
> ...

Why not bump up the MAJOR sccs number by one for the release.
Suppose that your current files are version 2.*
for all files
	get -r3 s.filename
	delta s.filename << COMMENT
	UPDATE VERSION FOR RELEASE 3
	COMMENT
	get s.filename
Since the specified release (-r3) is greater than what is in the file, the
current most recent version will be retrieved, but the new version will be
3.1. (See the almost unreadable table under the get(1) manual page!)