From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 23:57:39 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F80916A4CE; Mon, 20 Dec 2004 23:57:39 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44ADD43D58; Mon, 20 Dec 2004 23:57:39 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iBKNvat0007119; Mon, 20 Dec 2004 15:57:36 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iBKNvaZY007118; Mon, 20 Dec 2004 15:57:36 -0800 Date: Mon, 20 Dec 2004 15:57:36 -0800 From: Brooks Davis To: gnn@freebsd.org Message-ID: <20041220235736.GA6531@odin.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-net@freebsd.org Subject: Re: Dingo and PerForce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 23:57:39 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 19, 2004 at 01:23:43PM +0900, gnn@freebsd.org wrote: > Howdy, >=20 > For those who use PerForce and want to work on Dingo there is > now a dingo branch, named "dingo". The dingo branch contains > all of src, not just sys, as I suspect there are userland bits > we'll want to do. I know I'll be doing userland things. What's the planned model for committing changes to the main dingo branch? The IPv6 ipfw patches I'm working with are probably ready for wider exposure. Also, for subsystems such as ip6fw that have no future, how agressive should we be about nuking them in dingo. My guess is not very because we don't want to hamper work that might need to modify the old stuff to be committed when we aren't entierly sure how much longer we'll be supporting the subsystem in cvs, but I think there's some arugment for a more agressive approach to reduce the amount of junk we have to look at. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBx2bvXY6L6fI4GtQRAnjZAKC6OKcXE3S12oldoRKIhEml+tAdAgCgjqQh /GAUA7kX1XtlJBoOL0Ii9aI= =eHhk -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1--