Return to BSD News archive
Xref: sserve comp.os.386bsd.development:533 comp.os.linux:35625 Newsgroups: comp.os.386bsd.development,comp.os.linux Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!zaphod.mps.ohio-state.edu!menudo.uh.edu!uuneo!sugar!peter From: peter@NeoSoft.com (Peter da Silva) Subject: Re: PLEA across the board. Organization: NeoSoft Communications Services -- (713) 684-5900 Date: Fri, 23 Apr 1993 23:46:48 GMT Message-ID: <C5ynE2.1t3@sugar.neosoft.com> References: <jmonroyC5rz7x.LA1@netcom.com> <C5t95t.Ft3@sugar.neosoft.com> <SCT.93Apr21213242@damsay.dcs.ed.ac.uk> Lines: 17 In article <SCT.93Apr21213242@damsay.dcs.ed.ac.uk> sct@dcs.ed.ac.uk (Stephen Tweedie) writes: > In article <C5t95t.Ft3@sugar.neosoft.com>, peter@NeoSoft.com (Peter da Silva) writes: > > Put a string in that can be grepped for with "what". > Why not just do it the RCS way, and have a "$Id:$" string in any > modules you want to identify. That's exactly the *same* solution, except for RCS instead of SCCS. The problem with "what" and "ident" is they give you *all* the ID strings in the program, rather than just the one for the mainline. Hence my suggestion for a "what -q" (or ident -q). -- Peter da Silva. <peter@sugar.neosoft.com>. `-_-' Har du kramat din varg idag? 'U` My Apple-II has more RAM than my Mac!