From owner-freebsd-hackers Thu Feb 29 13:23:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA10298 for hackers-outgoing; Thu, 29 Feb 1996 13:23:25 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA10260 for ; Thu, 29 Feb 1996 13:22:20 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id NAA04347; Thu, 29 Feb 1996 13:16:33 -0800 (PST) To: Terry Lambert cc: nate@sri.MT.net (Nate Williams), dufault@hda.com, hackers@FreeBSD.ORG Subject: Re: How to use the sup'd CVS tree? In-reply-to: Your message of "Thu, 29 Feb 1996 11:18:54 MST." <199602291818.LAA11890@phaeton.artisoft.com> Date: Thu, 29 Feb 1996 13:16:33 -0800 Message-ID: <4345.825628593@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG Precedence: bulk > This is right. It is one of the most annoying attributes of the SUP/CVS > setup. Really, you want the changes to come in as commit deltas and > then recommit them to your local CVS tree so you can locally use things > like vendor branches and revision tags. CTM doesn't buy you this either. I'm totally serious when I say that I'd be very interested to hear your ideas on this. I'd be the first to say that our current source code control and distrubtion picture could be a lot better and more intuitive than it is, but the old problem of having to make due with the materials available has generally taken precedence over engineering ideals. That's not to say we can't roll our own replacement (or adapt an existing system to our needs), but we should at least be clear on the design parameters of what we'd like, first. The whole CVS vs P3 vs ??? issue will be coming up fairly shortly anyway, trust me. It's not a bad time to be thinking about what we'd _like_ as opposed to what we're forced to settle for. Jordan