From owner-freebsd-embedded@FreeBSD.ORG Sat Nov 15 16:59:26 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA7831065686; Sat, 15 Nov 2008 16:59:26 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id AD57A8FC13; Sat, 15 Nov 2008 16:59:26 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id mAFGwiKe080812; Sat, 15 Nov 2008 09:58:44 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 15 Nov 2008 10:00:02 -0700 (MST) Message-Id: <20081115.100002.-1384053695.imp@bsdimp.com> To: bms@incunabulum.net From: "M. Warner Losh" In-Reply-To: <491EE062.2070705@incunabulum.net> References: <491EE062.2070705@incunabulum.net> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-embedded@freebsd.org, freebsd-mips@freebsd.org Subject: Re: MIPS port repository question X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2008 16:59:27 -0000 In message: <491EE062.2070705@incunabulum.net> Bruce Simpson writes: : Hi, : : Apologies for cross-post: : I'm confused about which repository we should be doing active MIPS : development in. : : Should we still be using Perforce for this? : : I would like to push back my changes to bfe(4) which enable it to probe : and attach to the Sonics SiliconBackplane in the BCM5365P, currently : these are in an SVN checkout of HEAD on my main dev box. : : I see gonzo@ is active on the SiBa stuff right now... go gonzo! Most of the mips stuff has been pushed into the tree. The bleeding edge stuff is still just in p4. I didn't merge your bfe(4) changes into svn, but if you have something that's stable, there's no reason not to do so. I'd commit to p4 first, then do the normal merge, personally, but it is up to you. The next IFC will take care of merging. Warner