Path: utzoo!utgpu!tmsoft!dptcdc!dpmizar!swrinde!cs.utexas.edu!tut.cis.ohio-state.edu!mailrus!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.unix.questions
Subject: Re: SCCS version control
Message-ID: <9125@smoke.BRL.MIL>
Date: 9 Dec 88 23:10:39 GMT
References: <3217@ingr.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Distribution: na
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

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.

Well, UNIX System V has a "comb" utility that can help combine deltas,
but if your project is organized like ours, you may want to do what we
plan to do, which is to run a massive find on the source tree and for
each SCCS archive, do a "get -e", remove the archive, and "admin -i" a
replacement archive with SCCS ID 1.1.  Something similar but not so
drastic could then be done for subsequent releases, so that there are
no unreleased changes in the archives except for the current
developmental work.