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:27:36 -0700 [thread overview]
Message-ID: <20040709212736.GA5669@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0407091512440.5899@stargazer.weeve.org>
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.
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?
thanks,
greg k-h
>
> So what is the appropriate place? Can you as a team please come up with a
> singular answer and at least consult all those who will be effected
> *before* you change your mind and implement those changes?
>
> Thanks,
> --
> Jason Wever
> Gentoo/Sparc Co-Team Lead
>
> --
> gentoo-dev@gentoo.org mailing list
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-09 21:29 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 [this message]
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
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=20040709212736.GA5669@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