public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "C. Brewer" <cbrewer@stealthaccess.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Speaking of new kernels being added to the tree
Date: Fri, 3 Oct 2003 17:41:27 -0700	[thread overview]
Message-ID: <20031003174127.2f0bc925.cbrewer@stealthaccess.net> (raw)
In-Reply-To: <1065209212.11728.2.camel@sfa234225.richmond.edu>

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

On Fri, 03 Oct 2003 15:26:52 -0400
Donnie Berkholz <spyderous@gentoo.org> wrote:

> 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 released
> at the same time as Alan Cox's third patchset for 2.4.22 etc etc, so the
> version numbers would not work out properly for third-party patchsets,
> and people wouldn't know when upgrades were available.

I had thought about that myself, and quite honestly figured two approaches-
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, or
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.org
every day, even though yall have consistently provided updated ebuilds darn
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 with
the useflags.


-- 
Chuck Brewer
Registered Linux User #284015
Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred.



[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-10-04  0:41 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03  9:36 [gentoo-dev] Speaking of new kernels being added to the tree Brad Laue
2003-10-03  9:54 ` Brad Laue
2003-10-03 18:12   ` C. Brewer
2003-10-03 19:26     ` Donnie Berkholz
2003-10-04  0:41       ` C. Brewer [this message]
2003-10-04  2:05         ` Donnie Berkholz
2003-10-04  3:50           ` C. Brewer
2003-10-03 15:34 ` Brian Jackson
2003-10-03 16:23   ` Brad Laue
2003-10-03 17:10     ` Brian Jackson
     [not found]   ` <3F7DA0C3.3000303@gentoo.org>
2003-10-03 17:10     ` Brian Jackson
2003-10-03 17:15       ` Jon Portnoy
2003-10-03 23:50   ` Luke-Jr
2003-10-03 23:58     ` Kurt Lieber
2003-10-04  0:01       ` Jason Stubbs
2003-10-04  2:16         ` Luke-Jr
2003-10-04  0:15       ` Luke-Jr
2003-10-04  2:25         ` Jon Portnoy
2003-10-04  3:56           ` Luke-Jr
2003-10-04  4:29             ` Jason Stubbs
2003-10-04 12:40               ` Stuart Herbert
2003-10-04 13:10                 ` Luke-Jr
2003-10-04 13:51                   ` Stuart Herbert
2003-10-04 14:04                     ` Luke-Jr
2003-10-04 14:15                       ` Stuart Herbert
2003-10-04 14:36                         ` Luke-Jr
2003-10-04 15:09                           ` Stuart Herbert
2003-10-04 17:20                             ` Luke-Jr
2003-10-04 17:58                               ` Marius Mauch
2003-10-04 15:56                           ` Patrick Börjesson
2003-10-04 17:29                             ` Luke-Jr
2003-10-04 18:27                               ` Patrick Börjesson
2003-10-04 23:38                                 ` William Kenworthy
2003-10-05  0:48                                   ` Patrick Börjesson
     [not found]                                   ` <200310050343.49697.sn.ml@bayminer.com>
2003-10-05  1:52                                     ` William Kenworthy
2003-10-05  2:39                                 ` Luke-Jr
2003-10-04 13:33                 ` Stroller
2003-10-04 14:08                   ` William Kenworthy
2003-10-04 14:21                     ` Luke-Jr
2003-10-04 14:14                   ` Luke-Jr
2003-10-04 16:50                   ` Peter Ruskin
2003-10-04 13:50                 ` Patrick Börjesson
2003-10-04 13:57                   ` Luke-Jr
2003-10-04 16:13                     ` Jon Portnoy
2003-10-04 17:25                       ` Luke-Jr
2003-10-04 23:28                       ` Jason Stubbs
2003-10-05  0:17                         ` Kumba
2003-10-05  0:25                           ` James Harlow
2003-10-05  0:38                             ` Jason Stubbs
2003-10-05  0:48                               ` James Harlow
2003-10-05  2:10                               ` Kumba
2003-10-05  2:27                                 ` Jason Stubbs
2003-10-05  2:06                             ` Kumba
2003-10-05  2:44                               ` Jason Stubbs
2003-10-05  4:54                             ` Jon Portnoy
2003-10-05  5:28                             ` Kevyn Shortell
2003-10-05  0:50                           ` Jason Stubbs
2003-10-05  2:43                           ` Luke-Jr
2003-10-05  3:04                             ` Kumba
2003-10-05 14:24                               ` Luke-Jr
2003-10-05  5:22                         ` Kevyn Shortell
2003-10-05 11:30                           ` Jason Stubbs
     [not found]                             ` <200310051741.28963.sn.ml@bayminer.com>
2003-10-05 14:47                               ` Jason Stubbs
2003-10-05 15:53                                 ` Luke-Jr
2003-10-05 16:05                                   ` Luke-Jr
2003-10-04 13:06               ` Luke-Jr
2003-10-04  6:16             ` Donnie Berkholz
2003-10-04  6:34     ` Kumba
2003-10-04  7:27     ` Kevyn Shortell
2003-10-04 13:16       ` Luke-Jr
2003-10-04  2:03   ` Stroller
2003-10-04  2:08     ` Donnie Berkholz
2003-10-04  4:08       ` Stroller
  -- strict thread matches above, loose matches on Subject: below --
2003-10-05 18:24 Sami Näätänen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031003174127.2f0bc925.cbrewer@stealthaccess.net \
    --to=cbrewer@stealthaccess.net \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox