From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24774 invoked by uid 1002); 4 Oct 2003 02:06:01 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 22609 invoked from network); 4 Oct 2003 02:06:01 -0000 From: Donnie Berkholz To: gentoo-dev@gentoo.org In-Reply-To: <20031003174127.2f0bc925.cbrewer@stealthaccess.net> References: <3F7D4315.1020900@gentoo.org> <3F7D4741.40603@gentoo.org> <20031003111254.15c5ef72.cbrewer@stealthaccess.net> <1065209212.11728.2.camel@sfa234225.richmond.edu> <20031003174127.2f0bc925.cbrewer@stealthaccess.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-fFyJJq6J/tJRluelLAiZ" Message-Id: <1065233159.17858.5.camel@sfa234225.richmond.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 03 Oct 2003 22:05:59 -0400 X-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-38.7, required 5, EMAIL_ATTRIBUTION, IN_REP_TO, PGP_SIGNATURE_2, QUOTED_EMAIL_TEXT, REFERENCES, REPLY_WITH_QUOTES, USER_AGENT_XIMIAN) Subject: Re: [gentoo-dev] Speaking of new kernels being added to the tree X-Archives-Salt: ad96263b-f6a0-4896-9b1c-c2bdbb6d543d X-Archives-Hash: 2009a854757f8d4ad208ed7aa638605d --=-fFyJJq6J/tJRluelLAiZ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2003-10-03 at 20:41, C. Brewer wrote: > On Fri, 03 Oct 2003 15:26:52 -0400 > Donnie Berkholz wrote: >=20 > > A problem is that people who release kernel patches do not do so at the > > same time (e.g. Con Kolivas's second patchset for 2.4.22 is not release= d > > at the same time as Alan Cox's third patchset for 2.4.22 etc etc, so th= e > > version numbers would not work out properly for third-party patchsets, > > and people wouldn't know when upgrades were available. >=20 > I had thought about that myself, and quite honestly figured two approache= s- > bump a revision on patch changes, which would have the side effect of > forcing an upgrade on people who don't require it, or more realistically, > people using sources other than vanilla you would assume to be atleast > tracking the changes somewhat, so as to be notified via the patchmaker, o= r > if a little blurb was added to the changelog when a patch was updated. > Currently, I still track changes in the dev-sources by browsing kernel.or= g > every day, even though yall have consistently provided updated ebuilds da= rn > near immediately. So if there was maybe a little info blurb people could > look at to know when a patchset was updated, it would work out better wit= h > the useflags. >=20 Ahh, but part of the point of having a package management system (a large part, IMHO) is so you _don't_ have to go track down the current versions of things you run. --=-fFyJJq6J/tJRluelLAiZ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQA/fisHXVaO67S1rtsRAh/zAJ9Ev+VW7DQ+ky4WCHDkUNNrOpvmHwCdHD+S 5Pg2bh21C7a/RRsj/h1VhKI= =4tzf -----END PGP SIGNATURE----- --=-fFyJJq6J/tJRluelLAiZ--