Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Dec 2001 19:14:03 +0000
From:      Nik Clayton <nik@freebsd.org>
To:        D J Hawkey Jr <hawkeyd@visi.com>
Cc:        Nik Clayton <nik@freebsd.org>, hackers@freebsd.org
Subject:   Re: Tangent for discussion: FreeBSD performs worse that Linux
Message-ID:  <20011211191403.B82053@canyon.nothing-going-on.org>
In-Reply-To: <20011210152414.A1367@sheol.localdomain>; from hawkeyd@visi.com on Mon, Dec 10, 2001 at 03:24:14PM -0600
References:  <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011210080032.A4215@canyon.nothing-going-on.org> <20011210152414.A1367@sheol.localdomain>

next in thread | previous in thread | raw e-mail | index | archive | help

--DKU6Jbt7q3WqK7+M
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 10, 2001 at 03:24:14PM -0600, D J Hawkey Jr wrote:
> > Doesn't mean that you need 100% coverage though.  If you produce
> > something that only gets in 80% of the patches that could be applied
> > back that's still better than what we have now.  And it makes it easier
> > for someone else to help out with the missing 20%.
>=20
> Huh? You completely list me with this. Are you trying to say that some
> feature of a patch that applies to just the last three of four prior
> releases is OK, 'cuz right now none are (except for security fixes to
> RELENG_(current - 1))?

I meant that any effort you put in is better than none.  For example, if
you decide to start producing patches for 4.4 that bring in some
features from -stable (e.g., delayed acks) that's far better than you
not doing it at all.

Don't feel that because you can't do everything you want to do that you
shouldn't do any of it.  If you get the ball rolling, and become known
as *the* place to go for extra patches, you'll find that other people=20
start sending you additional patches to include.

Pretty soon we'll get bored of having people ask "Hey, why aren't these
patches in RELENG_4_4" (or whatever) and we'll corral you in to becoming
a committer so that you can make this an 'official' part of FreeBSD.

> > > So far, I've made three patchfiles that can be applied to 4.2REL and =
4.3REL.
> > > Not exactly the repertoire one would need to garner interest and mome=
ntum.
> >=20
> > It's a start.  What's the URL?
>=20
> You're kidding, right? I only started thinking about doing this yesterday!
> The patches are sitting right here, in $(HOME)/projects.

OK.  Well, if you put them up on a web site, we can link to them.  If
you can think of appropriate other places on the FreeBSD web site to
mention them then we can do that too.

Don't be put off because you want to start small. . .

N
--=20
FreeBSD: The Power to Serve             http://www.freebsd.org/
FreeBSD Documentation Project           http://www.freebsd.org/docproj/

          --- 15B8 3FFC DDB4 34B0 AA5F  94B7 93A8 0764 2C37 E375 ---

--DKU6Jbt7q3WqK7+M
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjwWWvsACgkQk6gHZCw343XVaQCfetcqL25P3KrxR3kJR4G+IsOp
BRAAn0XwmZzN5mToBxSM0yYEk5iy5GHi
=xQXn
-----END PGP SIGNATURE-----

--DKU6Jbt7q3WqK7+M--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011211191403.B82053>