From owner-freebsd-hackers Thu Apr 2 19:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04434 for freebsd-hackers-outgoing; Thu, 2 Apr 1998 19:09:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04423 for ; Thu, 2 Apr 1998 19:09:27 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id UAA02251; Thu, 2 Apr 1998 20:09:23 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd002176; Thu Apr 2 20:09:14 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA21161; Thu, 2 Apr 1998 20:09:12 -0700 (MST) From: Terry Lambert Message-Id: <199804030309.UAA21161@usr04.primenet.com> Subject: Re: Annother patch for Mozilla To: chuckr@glue.umd.edu (Chuck Robey) Date: Fri, 3 Apr 1998 03:09:12 +0000 (GMT) Cc: opsys@mail.webspan.net, hackers@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Apr 2, 98 07:58:42 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > this is why i think someone needs to start a CVS tree for the source. > > The patches are starting to fly. :) > > > > So again *prod* *prod* anyone with the resources care to start a mozilla > > CVS tree? *prod* *prod* > > It seems to me that, in offering to be a clearing house for patches > itself, and announcing they are starting a cvs tree too, the netscape > folks have a clear right to be kinda insulted at this. Why not use > their services? If they later prove to be insufficient, then maybe this > might be justified, but not without some reason. It seems to me that the FreeBSD folks working on Mozilla will have the same problem with this setup that I have with the FreeBSD setup: an inability to maintain local patche streams with history. So long as there are two or more versions of FreeBSD being maintained, it kind of makes sense to maintain a FreeBSD repository. Of course, if CVSup were modified to bring changes in on a continuously updated vendor branch, and tag when it did it, it would be a hell of a lot easier to make and track local changes in your CVS tree without them getting stomped by CVSup. In fact, I wish CVSup would do this for people supping FreeBSD and making large amounts of local mods (as I do), just as it would benefit FreeBSD users CVSup'ing from a FreeBSD repository that CVSup'ed from a Mozilla repository (presuming they set up a server at their site). Mozilla -> Vendor Branch (vendor=Mozilla) FreeBSD -> Vendor Branch (vendor=FreeBSD) ... Ad infinitum... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message