Path: utzoo!attcan!uunet!ogicse!husc6!paperboy!meissner
From: meissner@osf.org (Michael Meissner)
Newsgroups: comp.lang.c
Subject: Re: SCCS REVISION HISTORY
Message-ID: <MEISSNER.90Oct24151352@osf.osf.org>
Date: 24 Oct 90 19:13:52 GMT
References: <143950@sun.Eng.Sun.COM> <5633@abaa.UUCP>
Sender: news@OSF.ORG
Organization: Open Software Foundation
Lines: 32
In-reply-to: korsberg@abaa.uucp's message of 22 Oct 90 12:04:50 GMT

In article <5633@abaa.UUCP> korsberg@abaa.uucp (Ed Korsberg) writes:

| I have not used RCS but I incorporate revision strings in my source files
| by including the following line for C source files:
| 
| /****************************************************************************
|  Copyright 1990 Your company name
|  %W%, Date %G%
| *****************************************************************************/
| 
| Assuming the source file is named foobar.c  the above line %W%, Date %G%
| will expand to
|         @(#)foobar.c  1.7, Date 10/22/90
|                       ^ ^
| Major revision--------! !
| Minor revision----------!
| 
| This expansion is done when SCCS checks a file back into the database.

But this is not what was asked for.  Under RCS, you have a line with
$Log$ in it, RCS will copy the contents of the reason for the change
into the file at that point, keeping a running history of the changes
made to the file since it was created (or until you delete the log
entries manually).

Without building programs that sit on top of sccs, I don't know of
anyway to automagically add the revision history.
--
Michael Meissner	email: meissner@osf.org		phone: 617-621-8861
Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142

Do apple growers tell their kids money doesn't grow on bushes?