public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] kernel team:  please make up your mind
Date: Fri, 9 Jul 2004 23:32:38 +0100	[thread overview]
Message-ID: <20040709233238.6f090627@snowdrop.home> (raw)
In-Reply-To: <20040709212736.GA5669@kroah.com>

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

On Fri, 9 Jul 2004 14:27:36 -0700 Greg KH <gregkh@gentoo.org> wrote:
| 	- development-sources are clean kernel.org kernels

Since when? This is not what we were told when John helped us to move
our sparc patchset from sparc-dev-sources to his shiny new kernel-2
powered development-sources. We were given lengthy assurances that we
would a) be able to keep our sparc patchset there without having to
worry about it b) conflicting with the horridly broken gentoo- patchset
and c) it being repeatedly broken by people doing "security bumps".

We already know that c) hasn't been happening, and our requests for
certain people to show more care when dealing with other archs have
fallen upon deaf ears. Now we're being told that a) and b) are no longer
any good either?

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

Of course it's a big deal. We've already made our users change kernel
sets once. Now we're going to have to go through all this again because
the kernel team don't talk to each other? And you also expect us to deal
with people who assume that anything labeled gentoo-dev-sources will
include the gentoo- patchset?

| I am willing and able to help the sparc team (and any other arch) to
| make the g-d-s package work for them.

This is exactly what John told us when we switched from s-d-s to d-s.
What assurances do we have that we are not going to be screwed over yet
again the next time your team randomly decides to change policy without
informing anyone? We had these promises already about five kernel minor
versions ago.

To be honest, given the history on this, I think the ideal solution for
this would be an arch-dev-sources which was locked in cvs so that
over-zealous x86-kernel and security people *couldn't* go and break our
kernels *yet again*. I really don't like the implications that we don't
trust other developers on this, but having our kernel being broken three
times in two minor version versions is completely unacceptable.

-- 
Ciaran McCreesh : Gentoo Developer (Sparc, MIPS, Vim, Fluxbox)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm

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

  parent reply	other threads:[~2004-07-09 22:34 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
2004-07-09 23:01           ` Jason Wever
2004-07-09 22:32   ` Ciaran McCreesh [this message]
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=20040709233238.6f090627@snowdrop.home \
    --to=ciaranm@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