public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@gentoo.org>
To: Gentoo Dev Mailing List <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] kernel team:  please make up your mind
Date: Fri, 9 Jul 2004 15:29:01 -0700	[thread overview]
Message-ID: <20040709222901.GA6610@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0407091614320.5899@stargazer.weeve.org>

On Fri, Jul 09, 2004 at 04:17:45PM -0600, Jason Wever wrote:
> On Fri, 9 Jul 2004, Greg KH wrote:
> 
> > There was a bug marked for this.  Sorry for being quick on it.  I was
> > also told a while ago that the sparc team had their own kernel.  I never
> > thought it was this one (as the metadata file sure didn't say that...)
> 
> If I'm thinking of the same bug here, the sparc patch had nothing to do
> with it.  It wasn't even being used on the user's architecture.  As far as
> I know the user never really said it was fixed either.
>  
> > > > 	- development-sources are clean kernel.org kernels
> 
> Isn't this what vanilla-sources is for?

It would be, but we don't have a 2.6 kernel in that package for some
reason.  If we can do that somehow, that would be fine with me.  John,
any problem with this instead?

And if we do this, we can get rid of the development-sources pacakge
entirely :)

> > > > 	- gentoo-dev-sources are the current 2.6 kernel trees for all
> > > > 	  arches.  There is no cesspool of patches in there, and it is
> > > > 	  the kernel for the ppc64, amd64, x86, and a few other arches.
> > > > 	  Making it the sparc kernel too is no big deal.
> 
> When we make changes like this in the future, please give us some headway.
> 
>  
> > Again, sorry for the speed at which this happened, I am very sorry about
> > it.
> 
> Not to be a totally insensitive person, but until we have a chance to get 
> the patch worked into g-d-s, I'd strongly ask that the changes to 
> development sources be reverted.

Ok, it's reverted now.

Any timeline for sending the patches to me for g-d-s?  If you have a
pointer to them, I'll add them myself.

thanks,

greg k-h

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2004-07-09 22:31 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
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 [this message]
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=20040709222901.GA6610@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