From owner-freebsd-current  Wed Mar  6 18:20:35 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA01064
          for current-outgoing; Wed, 6 Mar 1996 18:20:35 -0800 (PST)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA01005
          Wed, 6 Mar 1996 18:20:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id SAA25870; Wed, 6 Mar 1996 18:20:41 -0800
Message-Id: <199603070220.SAA25870@Root.COM>
X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol
To: Daniel.M.Obrien@att.com
cc: ejc@naserver1.cb.att.com, freebsd-current@FreeBSD.org,
        committers@FreeBSD.org
Subject: Re: Paul's rules of order for committers (Re: -current submitting policys) 
In-reply-to: Your message of "Wed, 06 Mar 1996 16:41:51 EST."
             <9603062141.AA10817@cbsky.cb.att.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Wed, 06 Mar 1996 18:20:41 -0800
Sender: owner-current@FreeBSD.org
Precedence: bulk

>My minds eye suggests the process being followed is 1) make change, 2) submit,
>3) try it, 4) ``Oops'', 5) make new change, 6) submit, 7) try it....
>This is based on my anecdotal observations of submits.

   Of course it's not at all this simple. There's a lot more to the process
than meets the eye. Most of the FreeBSD developers have fairly lousy Internet
connectivity and this can lead to portions of a patch being left out or
uncommitted. We (almost?) always test things before committing them, but
what works on my machine may very well not work on yours and the reasons for
this can be extremely complex.
   Of course there is room for improvement, but I think we generally have very
high standards for our source code management and I think most of the time we
do a pretty damn good job about it.

-DG

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