Date: Sat, 23 Mar 2002 00:23:06 +0100 From: Wim Livens <wim@livens.net> To: "Matthew D. Fuller" <fullermd@over-yonder.net> Cc: francisv@dagupan.com, freebsd-isp@FreeBSD.ORG Subject: Re: [OT] Revision control system Message-ID: <20020322232306.GA35947@krijt.livens.net> In-Reply-To: <20020320012636.C29148@over-yonder.net> References: <10F29E27A956D511B0940050DA8D86A934101D@apmail.dagupan.com> <20020320012636.C29148@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Op wo 20 mrt, 2002 om 01:26:36am -0600, schreef Matthew D. Fuller: > I messed with RCS for a while, but it quickly showed its inherent > impracticality. I just use CVS for everything nowadays, with a single > central repository accessed via ssh from elsewhere. As a system administrator I often want to keep revision control on some configuration files. I just use "ci -l" for this. And ok, playing with permissions, I even get it working for multiple users but it's not optimal. My point is that all RCS/CVS documentation I've read assumes a typical code-development environment where each user checks out a local copy in his own directory. For configuration files, the situation is different, the checked out file must always reside in a certain directory and remain checked out at all times. Multiple users must be able to check it in to commit their changes. Am I missing something ? -- Wim Livens To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020322232306.GA35947>