From owner-cvs-src@FreeBSD.ORG Fri Mar 26 23:23:00 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EDD316A4CE; Fri, 26 Mar 2004 23:23:00 -0800 (PST) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBD9543D31; Fri, 26 Mar 2004 23:22:59 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.12.11/8.12.10) with ESMTP id i2R7MxJX085638; Fri, 26 Mar 2004 23:22:59 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i2R7Mx3X085637; Fri, 26 Mar 2004 23:22:59 -0800 (PST) (envelope-from obrien) Date: Fri, 26 Mar 2004 23:22:59 -0800 From: "David O'Brien" To: juli mallett Message-ID: <20040327072259.GA85580@dragon.nuxi.com> References: <200403261846.i2QIkVuT063179@repoman.freebsd.org> <200403261706.46836.jhb@FreeBSD.org> <20040326223518.GA78950@dragon.nuxi.com> <4064ED3E.4000407@freebsd.org> <20040327063641.GA85117@dragon.nuxi.com> <20040327071459.GA98009@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040327071459.GA98009@FreeBSD.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-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 cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: Scott Long cc: cvs-all@FreeBSD.org cc: John Baldwin Subject: Re: cvs commit: src/sys/boot/i386/boot0 boot0ext.s src/sys/boot/i386/boot0ext Makefile X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Mar 2004 07:23:00 -0000 On Fri, Mar 26, 2004 at 09:14:59PM -1000, juli mallett wrote: > > > >>This has a bug that I've fixed in a p4 branch. You could have > > > >>found that out if you had asked me first. > > > > > > > >I plan to commit what you have from p4. But I wanted this to be an > > > >exact copy of rev 1.22, so that if we can agree to go with the 2-sector > > > >boot0 for 6.0, it would be easier to see the changes. > > > > > > > >Please feel free to commit what you have in perforce, since it will be a > > > >little bit until I can. > > > > > > Since you seem to be concerned about preserving history, could bringing > > > this file back have been done as a repo-copy? > > > > Not as you might expect. I expect for 6.0, that 'boot0.s' will be the > > 2-sector one. Thus there will a diversion fork, I can't think of a way > > around it. But I'm trying to make it as easy to follow as possible. > > If this is JHB's thing, and he's got it in P4, wouldn't it be > better to let him take the lead and coordinate this than doing it > in some way you find convenient? Sorry, but I'd like to have a useful boot0 -- one that tells me my partition is something other than "???". That can't be done with a 1-sector boot0. No one complained when boot0sio.s was added, I don't see why boot0ext.s is becoming a federal case. Geez. I figured people would have greatly preferred how I did this vs. making boot0.s the 2-sector version. As far as I can tell, boot0 isn't at the top of JHB interest list right now. I personally have to tripple boot a laptop daily, so it is a large interest of mine. I also know of another committer who expressed interest in folding boot0sio.s into boot0ext.s so that we could 'cvs rm' boot0sio.s. > I'm not sure that having 3 places where the history of this file will > be is appealing, especially if you are making this fork in CVS for > purely an ephemeral manner. I do not find that a very attractive > solution. Perforce history does not exist. It is not the official project SCM. Things done in perforce are the same as things done on a committers private hard disk. Extracting things out of perforce is also a PITA. Again, things don't exist for the project unless they are in CVS. -- -- David (obrien@FreeBSD.org)