Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!kuhub.cc.ukans.edu!2fhdbeak
From: 2FHDBEAK@kuhub.cc.ukans.edu
Newsgroups: comp.sys.atari.st
Subject: Re: RCS for the ST (no, not yet)
Message-ID: <19925@kuhub.cc.ukans.edu>
Date: 16 Dec 89 16:59:52 GMT
References: <15412@laurel.athertn.Atherton.COM>
Organization: University of Kansas Academic Computing Services
Lines: 32

In article <15412@laurel.athertn.Atherton.COM>, alex@athertn.Atherton.COM (Alex Leavens) writes:
> Well, I've got my hot little hands on the source code for the original
> UNIX RCS system, and plan (in my copious spare time :-) to start porting
> it to the ST.  Anyone have any suggestions/comments/etc. to make about
> conventions I should follow, or other, similar things?
> 
> For example, I think that things are stored in RCS in the form
> <filename>.c,v
> which is fine for Unix, but...well, you know how the ST is.  I'd planned
> to change this to 
> <filename>.c_v
> 
> Any objections?
> 
> Cheers,
> 
> -- 
> --alex (TOO) ['My mind is my own'--#6]

A friend of mine (an Amiga developer) has RCS for the Amiga, and has given me
the source code for it.  

I haven't had time to port it yet, but the code doesn't look like it will have
to be changed at all (it was already altered to the Amiga Lattice C format,
which looks just like GNU C, the compiler I'll use).

Keep working on it, and keep in touch with me via E-mail so we can compare
progress.

--Jim Sisul
The University of Kansas
(I don't think I've expressed any opinions here, so why disclaim them?)