Path: utzoo!utgpu!attcan!uunet!tank!ncar!mailrus!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Newsgroups: comp.software-eng
Subject: Re: Version control across machines
Keywords: SCCS, porting, nightmare
Message-ID: <3849@bsu-cs.UUCP>
Date: 3 Sep 88 05:28:18 GMT
References: <832@vsi.UUCP>
Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Distribution: comp
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 16

In article <832@vsi.UUCP> sullivan@vsi.UUCP (Michael T Sullivan) writes:
>What I'm asking is, are there any
>references on how to keep version control between machines manageable?

I don't know how they do it, but here's one work-around.

Keep your master versions on a single machine that we will call the
"home" machine.  Transfer them to any other machine, but once a day (or
once a week, etc.) move everything back to the home machine and check
it in as a new version in an appropriate branch.  Software development
continues on the other machines and on those machines you could
continue to do version control locally.  Several quick revisions on a
remote machine might correspond to only one revision on the home
machine.
-- 
Rahul Dhesi         UUCP:  <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!dhesi