Xref: utzoo comp.unix.questions:13778 comp.sources.wanted:7498
Path: utzoo!attcan!lsuc!eci386!woods
From: woods@eci386.uucp (Greg Woods)
Newsgroups: comp.unix.questions,comp.sources.wanted
Subject: Re: naked SCCS really SCCS!
Summary: use of current directory is a non-issue
Keywords: SCCS, SystemV, sccs
Message-ID: <1989May21.145108.15654@eci386.uucp>
Date: 21 May 89 14:51:08 GMT
References: <297@tree.UUCP> <123@tdl.UUCP> <354@greek.UUCP> <160@cat.Fulcrum.BT.CO.UK> <8218@june.cs.washington.edu> <167@cat.Fulcrum.BT.CO.UK>
Reply-To: woods@eci386.UUCP (Greg Woods)
Organization: R. H. Lathwell Associates: Elegant Communications, Inc.
Lines: 29

In article <167@cat.Fulcrum.BT.CO.UK> tjo@fulcrum.bt.co.uk (Tim Oldham) writes:
> In article <8218@june.cs.washington.edu> ka@june.cs.washington.edu (Kenneth Almquist) writes:
> >tjo@Fulcrum.BT.CO.UK (Tim Oldham) writes:
> >> 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!
> 
> >OK, let's say you want to keep all your "s." and "p." files in a
> >subdirectory named sccs.  Say
> >	mkdir sccs		# create the directory
> >	admin -n sccs/s.file.c	# create an SCCS file
> >	get -e sccs/s.file.c	# get the file for editing
> >	emacs file.c		# edit the file
> >	delta sccs/s.file.c	# install changes
> 
> Yuck. I prefer the idea of SCCS doing this stuff for you. As far as I'm
> concerned, I shouldn't have to worry about how to store the previous
> versions - all this kind of stuff should be transparent in any UI worth
> its salt.

This is a non-issue.  Eric Allman's SCCS front-end "sccs" is
available on the BSD4.3-tahoe public tape (i.e. UUNET, etc.).
This front-end not only hides your files, but adds other
significant functionality.
-- 
						Greg A. Woods

woods@{{utgpu,eci386,ontmoh,tmsoft}.UUCP,gpu.utcs.UToronto.CA,utorgpu.BITNET}
+1-416-443-1734 [h]  +1-416-595-5425 [w]		Toronto, Ontario CANADA