public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] kernel team:  please make up your mind
Date: Fri, 9 Jul 2004 15:30:15 -0700	[thread overview]
Message-ID: <20040709223015.GB6610@kroah.com> (raw)
In-Reply-To: <200407091820.36454.vapier@gentoo.org>

On Fri, Jul 09, 2004 at 06:20:36PM -0400, Mike Frysinger wrote:
> On Friday 09 July 2004 06:17 pm, Jason Wever wrote:
> > > > > 	- development-sources are clean kernel.org kernels
> >
> > Isn't this what vanilla-sources is for?
> 
> yes and no
> vanilla is for 2.4

There's a 2.0 and 2.2 kernel in there too, how do people handle those?

> development is for 2.6

What's going to happen when 2.7 is released?

> we havent merged them via SLOT because portage would cause a lot of users to 
> 'upgrade' to 2.6 and we dont want that kind of bug reports on 
> forums/bugzilla/mailing lists

That wouldn't be such a bad thing to force to happen anyway :)

thanks,

greg k-h

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-07-09 22:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-09 21:15 [gentoo-dev] kernel team: please make up your mind Jason Wever
2004-07-09 21:27 ` Greg KH
2004-07-09 21:50   ` Jason Wever
2004-07-09 21:58     ` Greg KH
2004-07-09 22:17       ` Jason Wever
2004-07-09 22:20         ` Mike Frysinger
2004-07-09 22:30           ` Greg KH [this message]
2004-07-09 22:36             ` Mike Frysinger
2004-07-09 23:08               ` Greg KH
2004-07-09 23:39                 ` Grant Goodyear
2004-07-09 23:56                   ` Mike Frysinger
2004-07-09 23:56                   ` Greg KH
2004-07-09 22:29         ` Greg KH
2004-07-09 23:01           ` Jason Wever
2004-07-09 22:32   ` Ciaran McCreesh
2004-07-09 23:16     ` Greg KH

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=20040709223015.GB6610@kroah.com \
    --to=gregkh@gentoo.org \
    --cc=gentoo-dev@lists.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