From owner-freebsd-small Fri Jul 28 14:33: 6 2000 Delivered-To: freebsd-small@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 9F4DF37B68D for ; Fri, 28 Jul 2000 14:33:02 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13IHkS-000HTO-00; Fri, 28 Jul 2000 23:32:52 +0200 Date: Fri, 28 Jul 2000 23:32:52 +0200 From: Neil Blakey-Milner To: Albert Yang Cc: freebsd-small@FreeBSD.ORG Subject: Re: Structure? Message-ID: <20000728233252.A67144@mithrandr.moria.org> References: <39819359.5807.123A2B0@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39819359.5807.123A2B0@localhost>; from albert@achtung.com on Fri, Jul 28, 2000 at 02:06:17PM -0700 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 2000-07-28 (14:06), Albert Yang wrote: > OK guys, I was thinking we should throw together an agreed upon > structure for Pico? I was thinking we'd do like FreeBSD, have a > stable and a current; with maybe 4 releases to the stable tree every > year, or whenever we feel that a release is stable. Or we just follow the FreeBSD timetable, and use the FreeBSD -current and -stable branches, as usual. > Then we'd have a /make section which kept all the make > files against the modules. picobsd/share/mk, probably. I've got a few commits in store for continuing my existing work on the make(1) based system grog started, and I should have a document outlining my suggestions on advancing with PicoBSD. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message