Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mit-eddie!apollo!nazgul
From: nazgul@apollo.uucp (Kee Hinckley)
Newsgroups: comp.sys.apollo
Subject: Re: DSEE
Message-ID: <35b52901.b0a1@apollo.uucp>
Date: Fri, 26-Jun-87 17:33:00 EDT
Article-I.D.: apollo.35b52901.b0a1
Posted: Fri Jun 26 17:33:00 1987
Date-Received: Sat, 27-Jun-87 11:06:31 EDT
References: <3596c60e.b0a1@apollo.uucp> <1907@zeus.TEK.COM> <35b09127.d858@apollo1.uucp>
Reply-To: nazgul@apollo.UUCP (Kee Hinckley)
Organization: Apollo Computer, Chelmsford, MA
Lines: 25

In article <35b09127.d858@apollo1.uucp> heinzl_c@apollo1.uucp (Carl Heinzl) writes:
> DSEE does source management basically by keeping interleaved files (i.e.
> files with all the changes since the initial version).  In this way,

Incidentally.  It does this internally much the way RCS or SCCS does, via
a file that contains all of the changes.  However you never see that file.
When you want to modify a file you have to check it out (reserve it).  But
to read the file you can just use your favorite editor on the DSEE source
file directly.  What you see depends on what you asked for.

    If you edit "foo.c" you get the most recent version.
    "foo.c/[10]" will give you version 10.
    "foo.c/[SR9.5]" will give you the version you named SR9.5.

Any of those pathnames will look just like a normal text file to your tools,
even though there's only one file.

The magic of extensible streams.

                                                        -kee
-- 
UUCP: {mit-erl,yale,uw-beaver}!apollo!nazgul  ARPA: apollo!nazgul@eddie.mit.edu
I'm not sure which upsets me more; that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate 
everyone else's.