Date: Tue, 06 Jan 2004 22:22:04 -0500 From: Scott W <wegster@mindcore.net> To: Shawn Guillemette <shawn@guillemette.org> Cc: freebsd-questions@freebsd.org Subject: Re: RCS Message-ID: <3FFB7B5C.1030105@mindcore.net> In-Reply-To: <000801c3d3a7$c2d08330$6a01a8c0@tacstation> References: <000801c3d3a7$c2d08330$6a01a8c0@tacstation>
next in thread | previous in thread | raw e-mail | index | archive | help
Shawn Guillemette wrote: >Once apon a time I worked for a company that had used somthing called "RCS" to protect files from being writen to by more then one user at the same time. > > > >Im now in a situation where that would become helpful. I have read the man pages on RCS and looked for documantation on the web including the FreeBSD diary site and wanted to post to you all to see if anyone had any links to some good documentation on this. Even how-to's would be great. > >Thanks > >Shawn >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > > It's old, it's not up to date, but neither is RCS ;-) http://www.bookpool.com/.x/rxmsgjmgri/sm/1565921178 RCS is fine for dealing with 1-2 people accessing files, but if you're thinking of using it for a larger project with network support, you may really want to look at something like CVS (free) or Perforce (current favorite commercial SCM).... There really isn't a significant amount involved in RCS. man ci, co, rcs and understand branching. Add a few more people and then wait until you wind up wrapping all of the rcs commands in shell scripts.... Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FFB7B5C.1030105>