From owner-freebsd-mobile Tue Jun 22 0:30:32 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9A13814E80 for ; Tue, 22 Jun 1999 00:30:28 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA71106; Tue, 22 Jun 1999 01:30:14 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA04597; Tue, 22 Jun 1999 01:28:17 -0600 (MDT) Message-Id: <199906220728.BAA04597@harmony.village.org> To: "William Woods" Subject: Re: PAO3 into the tree Cc: mobile@FreeBSD.ORG In-reply-to: Your message of "Mon, 21 Jun 1999 22:06:27 PDT." <000101bebc6c$fbcda200$114b93cd@william> References: <000101bebc6c$fbcda200$114b93cd@william> Date: Tue, 22 Jun 1999 01:28:17 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <000101bebc6c$fbcda200$114b93cd@william> "William Woods" writes: : How does this branch differ from the RELENG_3 branch? It is FreeBSD 3.2 Release plus the PAO3 project's patches to 3.2. : Is what you are saying : that if we want a PAO system, we should change out tag to RELENG_3_2_PAO : then? Not necessarily. Right now it is what I say that it is. : What special is needed to compile the PAO in to the regular source or : is all that merged now? Right now you *should* be able to just rebuild the world with a tree checked out from the RELENG_3_2_PAO branch and use a kernel from there. : Also, how closely will this track the RELENG_3 branch? The long-term goal is for the differences between FreeBSD PAO and plain FreeBSD to lessen. The RELENG_3_2_PAO branch is intended to facilitate this goal. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message