Date: Mon, 20 Dec 2004 15:57:36 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: gnn@freebsd.org Cc: freebsd-net@freebsd.org Subject: Re: Dingo and PerForce Message-ID: <20041220235736.GA6531@odin.ac.hmc.edu> In-Reply-To: <m2wtveex0w.wl@minion.local.neville-neil.com> References: <m2wtveex0w.wl@minion.local.neville-neil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041220235736.GA6531>