From owner-cvs-all  Wed Dec  2 21:05:37 1998
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA28951
          for cvs-all-outgoing; Wed, 2 Dec 1998 21:05:37 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28946;
          Wed, 2 Dec 1998 21:05:35 -0800 (PST)
          (envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.1/8.9.1) id VAA21338;
	Wed, 2 Dec 1998 21:05:19 -0800 (PST)
	(envelope-from dillon)
Date: Wed, 2 Dec 1998 21:05:19 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199812030505.VAA21338@apollo.backplane.com>
To: Eivind Eklund <eivind@yes.no>
Cc: Nate Williams <nate@mt.sri.com>, cvs-committers@FreeBSD.ORG,
        cvs-all@FreeBSD.ORG
Subject: Re: proposal: simple cvs mod to handle shared checked-out source trees
References: <199812022200.OAA19221@apollo.backplane.com> <199812022209.PAA08774@mt.sri.com> <199812022258.OAA19488@apollo.backplane.com> <199812022303.QAA09143@mt.sri.com> <19981203021233.A18661@follo.net>
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk


:Commonly used everywhere I've worked.  And this is not because I
:initate it; I specifically try to get people to not do this unless it
:is clearly the most efficient way for them to work, and I can not
:remember ever having made the suggestion.
:...
:
:Eivind.

    At NextBus the source tree is checked out on each workstation and
    people (usually) login as themselves on whatever workstation they
    are sitting at, cvs update -d, and then work on it.  Ugh.

    Even at BEST the traditional local source tree under CVS is checked
    out in only one place on one machine, but unlike the active network
    config and dns files these sources are only worked on by 3 people.  It
    just turns out to be easier to have only one copy checked out and have
    it happen to be the same copy that we use to generate the system.

    The network and DNS management works differently... the background 
    system announces when it is about to do a sync and any staff member
    (out of 20+ or so people) who is actively messing with the working set 
    cleans up whatever he is doing and then waits for the system to sync
    before resuming.

    I can definitely see the utility even when working on a traditional
    source project, where you might have a small sub-group of people working
    on a specific feature using a common working dataset.  Even though the
    dataset is separate from other things other people are working on,
    you can still have the situation where several people clump together
    on a common dataset.  A small group of two or three people can often
    work on a common (traditional source) working tree without stepping
    on each others toes.

					    -Matt


    Matthew Dillon  Engineering, HiWay Technologies, Inc. & BEST Internet 
                    Communications & God knows what else.
    <dillon@backplane.com> (Please include original email in any response)    

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message