Path: utzoo!attcan!uunet!husc6!purdue!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: RCS
Message-ID: <12294@mimsy.UUCP>
Date: 2 Jul 88 23:33:40 GMT
References: <3493@rpp386.UUCP> <23585@teknowledge-vaxc.ARPA>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 28

In article <23585@teknowledge-vaxc.ARPA> mkhaw@teknowledge-vaxc.ARPA
(Mike Khaw) writes:
>1.2
>log
>@can't embed Log in shell script (no syntax for multiline comments)
>@

It is true that the shells do not have true multiline comments, but
that should not stop you from including the $Log$ keyword in an RCS
file.  RCS knows how to prefix log messages with strings; if the
`comment leader' RCS chooses is incorrect, you can set it directly
with the `rcs' command.  Even if that were not the case, one could
write, e.g.,

	: << \eof
	$Log$
	eof			(`\eof' in csh)

although this is a kludge.

[light camping stove]
That said, I still think putting log messages in source files is wrong.
The log messages (in SCCS, delta messages) belong in the RCS file.
[put out camping stove]
We now return you to your regularly scheduled flamage.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris