*BSD News Article 15723


Return to BSD News archive

Xref: sserve comp.os.386bsd.development:690 comp.os.linux:37652
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!howland.reston.ans.net!agate!agate.berkeley.edu!cgd
From: cgd@gaia.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.development,comp.os.linux
Subject: Re: PLEA across the board.
Date: 6 May 93 05:33:29
Organization: Kernel Hackers 'r' Us
Lines: 23
Message-ID: <CGD.93May6053329@gaia.CS.Berkeley.EDU>
References: <jmonroyC5rz7x.LA1@netcom.com> <C5t95t.Ft3@sugar.neosoft.com>
	<SCT.93Apr21213242@damsay.dcs.ed.ac.uk>
NNTP-Posting-Host: gaia.cs.berkeley.edu
In-reply-to: sct@dcs.ed.ac.uk's message of Wed, 21 Apr 1993 21:32:42 GMT

In article <SCT.93Apr21213242@damsay.dcs.ed.ac.uk> sct@dcs.ed.ac.uk (Stephen Tweedie) writes:
=>Why not just do it the RCS way, and have a "$Id:$" string in any
=>modules you want to identify.  This way, the information is
=>automatically kept uptodate by RCS or CVS, and you can use the
=>existing "ident" command from RCS to identify both source and code
=>(assuming you have $Id$ string constants in your modules).

because when you "cvs export" a source tree, by default, it gets
rid of the dollar-signs, to make the version numbers of
an exported release "static" and importable into another
person's/group's environment...

i, for one, think this is a *very* good+important thing, but it
breaks ident...



chris
--
Chris G. Demetriou                                    cgd@cs.berkeley.edu

   "386bsd as depth first search: whenever you go to fix something you
       find that 3 more things are actually broken." -- Adam Glass