Xref: utzoo comp.unix.questions:13553 comp.sources.wanted:7370 Path: utzoo!attcan!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!mcvax!ukc!axion!fulcrum!tjo From: tjo@Fulcrum.BT.CO.UK (Tim Oldham) Newsgroups: comp.unix.questions,comp.sources.wanted Subject: Re: naked SCCS really SCCS! Keywords: SCCS, SystemV, obnoxious_program Message-ID: <160@cat.Fulcrum.BT.CO.UK> Date: 12 May 89 16:31:59 GMT References: <297@tree.UUCP> <123@tdl.UUCP> <354@greek.UUCP> <1580@auspex.auspex.com> Reply-To: tjo@fulcrum.bt.co.uk (Tim Oldham) Organization: BT I.T. Systems, Birmingham, England Lines: 26 In article <1580@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes: >>Bullshit. It has done a damn good job for me, and front-end interfaces just >>add more steps without adding appreciable functionality or ease of use. > >Bullshit. I find "admin" a pain to use; the BSD "sccs" front-end >program's "sccs create" and "sccs enter" programs make it much nicer - >it takes *fewer* steps to use them than to use full-frontal "admin". Hear hear. But the trouble with sysV sccs is the brain-damaged way it keeps all the s- and p-files in the directory you're working in. Crazy! Apart from anything else (directory clutter, making it harder to write shell scripts 'cos matching *.c doesn't work any more, etc.), SCCS ought to be transparent. And what's happened to fix? Wow, so I can cdc to change the delta commentary, but that's not a great deal of help. I always feel guilty using chmod, vi and admin -z around s-files, and quite right too. If anyone can tell me how to get sccs to use an SCCS directory, I'd be *extremely* grateful. Anyone have a fix program for sysV they can distribute? Tim. -- Tim Oldham ...!mcvax!ukc!axion!fulcrum!tjo or tjo@fulcrum.bt.co.uk #include Why have coffee, when caffeine tastes this good?