From owner-freebsd-smp Wed Jun 5 13:19:55 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA29672 for smp-outgoing; Wed, 5 Jun 1996 13:19:55 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA29664; Wed, 5 Jun 1996 13:19:52 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA29562; Wed, 5 Jun 1996 13:14:59 -0700 From: Terry Lambert Message-Id: <199606052014.NAA29562@phaeton.artisoft.com> Subject: Re: Unix/NT synchronization model (was: SMP progress?) To: phk@freebsd.org (Poul-Henning Kamp) Date: Wed, 5 Jun 1996 13:14:59 -0700 (MST) Cc: terry@lambert.org, sef@kithrup.com, smp@freebsd.org In-Reply-To: <1856.834001792@critter2.tfs.com> from "Poul-Henning Kamp" at Jun 5, 96 12:09:52 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >With respect, this is much more difficult for those of us who > >must do our changes locally and use SUP or CTM to keep up to > >date. > > Hey buddy, how do you think I work ???? I don't know; I just assumed that, like some of the other core team members, you put a branch tag on the real CVS tree and communicated changes between working groups that way. I remember a big discussion on CVS tag assignment on the -current list for using the CVS tree to communicate between people working on the same set of not-ready-for-prime-time code. > >Each time I pull an updated tree from my local mirror of the CVS > >tree, I must re-merge and re-integrate all of my patches. > > join the club. :-( And you don't find this intolerable when you get to 50,000 lines of patches in 4 different sub-areas so that you can agregate them and work on what you want to work on instead of eternally reintegrating the same sub-patches over-and-over-and-over...??? I got to the point, while I was working at Novell, that I spent all of my time integrating my patches and none of my time doing the work that the patches were supposed to support. It was worth leaving Novell and rewriting everything from scratch (to avoid "contamination") just to get to do real coding once again. It sucks out to have the tools put me back in the same position a year and a half after my escape. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.