From owner-freebsd-alpha Fri Sep 15 12: 4:11 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 692D637B42C for ; Fri, 15 Sep 2000 12:04:09 -0700 (PDT) Received: (qmail 52219 invoked by uid 1142); 15 Sep 2000 19:04:08 -0000 Date: 15 Sep 2000 12:04:08 -0700 Date: Fri, 15 Sep 2000 11:52:39 -0700 From: Jason Evans To: Matthew Jacob Cc: alpha@freebsd.org Subject: Re: PRE_SMPNG question.... Message-ID: <20000915115239.E7247@blitz.canonware.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mjacob@feral.com on Thu, Sep 14, 2000 at 07:17:54PM -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Sep 14, 2000 at 07:17:54PM -0700, Matthew Jacob wrote: > > If I want to make sure that PC164's boot and run in the source tree > that was tagged PRE_SMPNG, is it acceptable to MFC, as it were, the fix? > > I've had to, hah hah (coz I wasn't as careful as I should) spend most of the > day reinstalling 4.1 so I could get back to having some stable disks I can > actually boot from prior to moving ahead back into -current for alpha. It > strikes me that having the PRE_SMPNG stuff be stable would be good. > > But I'll admit that I'm a bit hazy as to how branches work vs. tags. PRE_SMPNG is a static tag. That means that the only way to modify the PRE_SMPNG version of a file is to move the tag to a different version of a file. So, unless the file hasn't changed since the PRE_SMPNG tag was created, moving the tag will prove very difficult. Indeed, the purpose of the PRE_SMPNG tag was not to provide a branch point; it was merely meant to mark the last moment before the SMP code destabilized the tree. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message