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 14:58:32 -0700	[thread overview]
Message-ID: <20040709215832.GA6155@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0407091545560.5899@stargazer.weeve.org>

On Fri, Jul 09, 2004 at 03:50:19PM -0600, Jason Wever wrote:
> On Fri, 9 Jul 2004, Greg KH wrote:
> 
> > On Fri, Jul 09, 2004 at 03:15:05PM -0600, Jason Wever wrote:
> > > Can we please get a consistent answer on 2.6 kernels when it comes to 
> > > sparc?  We used to have sparc-development-sources, which we were told to 
> > > consolidate into development-sources.  Now today with absolutely 0 
> > > notification what-so-ever, our patchsets to development-sources were 
> > > yanked because it wasn't the appropriate place.
> > 
> > Sorry for the stress.  There really isn't a kernel team anymore, becides
> > me and a few others, and we all seem strung accross different timezones
> > these days.
> 
> That's about the size of most of our teams.  What was so dire about the 
> sparc patch to development-sources that it had to be removed right this 
> instant without consulting both SPARC and your own kernel team?

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...)

> > Here's the answer:
> > 	- development-sources are clean kernel.org kernels
> > 	- 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.
> > 
> > This is needed so that bugs and security fixes that previously have not
> > gotten put into the d-s package get applied across all arches quickly
> > and easily.
> > 
> > I am willing and able to help the sparc team (and any other arch) to
> > make the g-d-s package work for them.
> > 
> > Is that acceptable?
> 
> Yes and no.  I'm definitely willing to help work with you to get that 
> patch set in there.  However that doesn't change the fact that the 
> adjustment of the packages today was very bad as it wasn't communicated at 
> all to allow us to at least notify our users that things will change.  
> Removing our patchset can and will cause problems for people who were 
> using development-sources on sparc, and more than just because they have 
> to switch what kernel they use.

But they get security fixes for free with that switch, that's a good
reason to do so :)

> If you want to make changes that's fine, just please consider the 
> ramifications of those changes and let the people who will be effected 
> know with enough time before-hand so that they can do what is needed to 
> help make those migration changes as smooth as possible.

Again, sorry for the speed at which this happened, I am very sorry about
it.

thanks,

greg k-h

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-07-09 22:00 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 [this message]
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
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=20040709215832.GA6155@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