From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Getting patches in (was: Re: Roles for distributions)
Date: Tue, 12 Sep 2000 19:13:42 -0400 [thread overview]
Message-ID: <20000912191342.A7444@drow.them.org> (raw)
In-Reply-To: <39BDD1E2.F0DC9B1D@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Tue, Sep 12, 2000 at 02:49:06AM -0400
On Tue, Sep 12, 2000 at 02:49:06AM -0400, Jeff Garzik wrote:
>
> Michel Lanners wrote:
> > I agree that this seems to be a major problem of the PPC Linux port at
> > this time. It is not clear at all how the flow of patches from user
> > contribution, to PPC kernel tree, to Linus' tree is happening... and
> > unfortunately, too often, it just isn't happening.
>
> Cort posted the following on linux-kernel, this past Thursday. (Cort
> quoted with ">", Till Straumann quoted with "}")
>
> > } Can somebody please tell me, who is currently maintaining
> > } arch/ppc?
> > }
> > } The link
> > }
> > } http://www.ppc.kernel.org/
> > }
> > } in the MAINTAINERS file is dead.
> > }
> > } Regards, Till
> >
> > It's unmaintained right now. The www.ppc.kernel.org site is gone.
> > Take a look at www.fsmlabs.com/linuxppcbk.html for the PPC tree.
Is someone planning to step up and take over, then, officially? Or is
Cort going to be back?
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-12 23:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-10 19:52 Roles for distributions Kevin B. Hendricks
2000-09-11 1:36 ` Ariel Rios
2000-09-11 13:14 ` Dan Malek
2000-09-11 13:33 ` Hendricks, Kevin
2000-09-11 14:03 ` Dan Malek
2000-09-11 14:11 ` Hendricks, Kevin
2000-09-11 23:06 ` Sriranga Veeraraghavan
2000-09-11 15:17 ` Daniel Jacobowitz
2000-09-11 17:32 ` Hendricks, Kevin
[not found] ` <200009111757.NAA23936@mal-ach.watson.ibm.com>
2000-09-11 18:04 ` Hendricks, Kevin
2000-09-11 19:16 ` Gary Thomas
2000-09-11 19:27 ` Hendricks, Kevin
2000-09-11 18:16 ` Hollis R Blanchard
2000-09-11 18:43 ` David A. Gatwood
2000-09-11 20:01 ` Todd Lipcon
2000-09-11 20:32 ` Dan Foster
2000-09-11 20:45 ` Todd Lipcon
2000-09-11 20:49 ` Michel Dänzer
2000-09-12 4:24 ` Graham Stoney
2000-09-12 6:14 ` Getting patches in (was: Re: Roles for distributions) Michel Lanners
2000-09-12 6:49 ` Jeff Garzik
2000-09-12 23:13 ` Daniel Jacobowitz [this message]
2000-09-12 8:59 ` Benjamin Herrenschmidt
2000-09-12 15:40 ` Dan Malek
2000-09-13 3:47 ` Paul Mackerras
2000-09-12 15:09 ` Roles for distributions mberglund
2000-09-12 20:55 ` Michael Schmitz
2000-09-12 21:36 ` mberglund
2000-09-12 22:09 ` Geert Uytterhoeven
2000-09-13 13:54 ` mberglund
2000-09-13 13:46 ` Michel Dänzer
2000-09-13 14:21 ` mberglund
2000-09-12 23:04 ` Daniel Jacobowitz
2000-09-11 21:00 ` Geert Uytterhoeven
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=20000912191342.A7444@drow.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).