Date: Thu, 10 Jul 1997 18:36:32 +0200 (CEST) From: Eivind Eklund <perhaps@yes.no> To: Mikael Karpberg <karpen@ocean.campus.luth.se> Cc: scott@statsci.com, jmacd@CS.Berkeley.EDU, current@FreeBSD.ORG Subject: Re: PRCS (was Re: CVS Branches hits again!) Message-ID: <199707101636.SAA04311@bitbox.follo.net> In-Reply-To: Mikael Karpberg's message of Thu, 10 Jul 1997 17:55:24 %2B0200 (CEST) References: <199707101415.HAA14077@knife.statsci.com> <199707101555.RAA11530@ocean.campus.luth.se>
next in thread | previous in thread | raw e-mail | index | archive | help
> > According to Scott Blachowicz: > > Josh MacDonald <jmacd@CS.Berkeley.EDU> wrote: > > > > > > [ PRCS ] > > > > > > > > > Some things it yet lacks are: > > > > > > > > > > 1) a client server environment > > > > > > > > Becoming more important as FreeBSD developers are now starting to use > > > > it. > > > > > > This is currently my first priority. I've kept pretty quiet and not > > > pushed PRCS in too many places because of this, but spoke up now because > > > I figure PRCS would be no worse than CVS since people seem to be using > > > CVSup. > > > > Well...for me, the client/server stuff has been pretty handy. I have a few > > small repositories that I maintain at work, but work on at home occasionally. > > It's handy to be able to specify things so that syncing with the remote > > repository goes through a ssh tunnel as opposed to requiring some form of NFS > > access or maintaing a copy of my _repository_. > > Speaking of this client/server thing. If you have a repository on one > machine and have a lot of developers that you want to give access into > the repository, but NOT into the machine otherwise, how do you do? Trivially - by setting the shell of the users in question to point at a file containing only #!/bin/sh /usr/bin/cvs server (Not actually tested, but I've done similar things) Eivind.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707101636.SAA04311>