From owner-freebsd-chat  Mon Dec  9 16:12:42 1996
Return-Path: <owner-chat>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id QAA17586
          for chat-outgoing; Mon, 9 Dec 1996 16:12:42 -0800 (PST)
Received: from www.hsc.wvu.edu (www.hsc.wvu.edu [157.182.105.122])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA17569
          for <chat@freebsd.org>; Mon, 9 Dec 1996 16:12:32 -0800 (PST)
Received: (from jsigmon@localhost) by www.hsc.wvu.edu (8.7.5/8.7.3) id TAA29904; Mon, 9 Dec 1996 19:11:14 -0500 (EST)
Date: Mon, 9 Dec 1996 19:11:14 -0500 (EST)
From: Jeremy Sigmon <jsigmon@www.hsc.wvu.edu>
To: Terry Lambert <terry@lambert.org>
cc: J Wunsch <j@uriah.heep.sax.de>, chat@freebsd.org, terry@lambert.org
Subject: Re: siguing into current from a random version
In-Reply-To: <199612092228.PAA01956@phaeton.artisoft.com>
Message-ID: <Pine.BSF.3.91.961209190821.29867C-100000@www.hsc.wvu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-chat@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Voila, we have destroyed all of the rocks behind which tree-breakers
> can hide.  If person A breaks the tree, it will be obvious that it
> is person A's fault, and the breakage can always be trivially undone
> by backing up one write-lock-label.

As an aside.
At work we would use RCS to check in and out web pages so we would not 
step on each other.  This worked until someone checked out a bunch of
pages that they were "working on" and a few typos needed to be fixed.
This locking feature quickly became annoying.  :(
I can definately see why the "volunteers" don't want to enable this.