From owner-freebsd-chat  Mon Dec  9 15:31:22 1996
Return-Path: <owner-chat>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id PAA10201
          for chat-outgoing; Mon, 9 Dec 1996 15:31:22 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA10191
          for <chat@FreeBSD.org>; Mon, 9 Dec 1996 15:31:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id PAA06087; Mon, 9 Dec 1996 15:26:06 -0800 (PST)
Message-Id: <199612092326.PAA06087@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: J Wunsch <j@uriah.heep.sax.de>
cc: chat@FreeBSD.org, terry@lambert.org (Terry Lambert)
Subject: Re: siguing into current from a random version 
In-reply-to: Your message of "Mon, 09 Dec 1996 22:07:30 +0100."
             <199612092107.WAA24141@uriah.heep.sax.de> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 09 Dec 1996 15:26:06 -0800
Sender: owner-chat@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>As Terry Lambert wrote:
>
>> Heh.  Like checking code in without compiling the tree as it would
>> look following the checkin...
>> 
>> Nothing you can do about that, really, without instituting global
>> writer locks on the tree (not that this will ever be approved).
>
>Do the global writer locks compile the tree for me?  Then i'm all for
>it! :-)
>
>Otherwise: moot point, i'd say...  I can barely remember that we've
>been suffering from two people hammering at the tree at the same spot,
>and causing inconsistencies by this.  99.9 % of the problems have been
>human errors.

   In fact, in the history of the project, I don't think it has ever occurred.
The mistakes I was refering to are botched diffs and incomplete commits.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project