From owner-freebsd-current Sun Mar 17 8:45:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 1FB3037B4ED; Sun, 17 Mar 2002 08:45:06 -0800 (PST) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.2/8.12.2) with ESMTP id g2HGj6lv010994; Sun, 17 Mar 2002 08:45:06 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.2/8.12.2/Submit) id g2HGhph6010971; Sun, 17 Mar 2002 08:43:51 -0800 (PST) Date: Sun, 17 Mar 2002 08:43:51 -0800 From: "David O'Brien" To: Terry Lambert Cc: re@FreeBSD.org, current@FreeBSD.org Subject: Re: HEADS UP: -CURRENT Feature Slush is OVER Message-ID: <20020317084351.C10393@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <20020316111818.GO17499@freebsdmall.com> <1016289691.91096.2.camel@notebook> <20020316115309.E95652@dragon.nuxi.com> <3C93C273.8356D01@mindspring.com> <20020317083315.GO19657@freebsdmall.com> <3C945D1B.61ECDDD3@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C945D1B.61ECDDD3@mindspring.com>; from tlambert2@mindspring.com on Sun, Mar 17, 2002 at 01:08:43AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Mar 17, 2002 at 01:08:43AM -0800, Terry Lambert wrote: > Imagine that you have the developer's prerelease, and you > have a bug (because you're a developer who's using the > pre-release). > > Now say you have become involved in the process, because the > pre-release has done it's job. You want to fix the bug. > > In order to do this, you are going to need the delta against > the developer's prerelease source tree. To get this, the > process is: > > 1) Before you make any changes, copy /usr/src to /usr/src.org > OR > mv /usr/src/usr/src.new > reinstall /usr/src using /stand/sysinstall > mv /usr/src /usr/src.org > mv /usr/src.new /usr/src > > 2) Make your changes > > 3) Run diff -cr /usr/src/org /usr/src > > 4) Now, figure out how to apply these diffs to the CVSup > image of the -current CVS tree for some checked-out > version of -current And just HOW is this different from previous snapshot CD's? You have the source tarball w/no CVS/ directories. To fix your bug, you have to do these SAME exact steps. I see ZERO difference. You imply that maybe RE's fixed some bug in only the code for the CD and not in the CVS tree. Maybe you don't know that only pieces of bits that are CVS will be in the src tarball. Thus just like any snapshot CD source, you have to figure out if someone in has backed out a change in the CVS repo, etc.. Again, NO change from the past. Geez people. It was nice in the past when the snapshot CD's were done by a private company where none of us got to see how it was produced. Now that the process is more open, people want to try to railroad the effort. And people wonder why many companies and organization have real concerns about opening up source bases and procedures.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message