linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: <mlan@cpu.lu>, <linuxppc-dev@lists.linuxppc.org>,
	<greyham@research.canon.com.au>
Subject: Re: Getting patches in (was: Re: Roles for distributions)
Date: Tue, 12 Sep 2000 10:59:18 +0200	[thread overview]
Message-ID: <20000912085918.23901@192.168.1.10> (raw)
In-Reply-To: <200009120614.IAA00922@piglet.grunz.lu>


>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.
>
>I've sent lots of patches to those people I thought were 'platfor
>maintainers', only to notice weeks or months later, that a few kernel
>releases later they were not in there. Patches just disappeared into the
>void, no reaction at all. _That_ is frustrating. If patches are refused
>for some reason, then fine, I've not done my homework, let me try again.
>But without any reaction, I haven't even gotten that chance.

That problem is not specific to the PPC port, how many times patches are
sent to Linus without an answer, but without anything happening neither.

The fact is that there are about 4 or 5 people from this list who can
feed things in the main PPC tree (Paul, Cort, Geert, Dan, me, I may be
missing others) and Linus/Alan usally get patches from Paul or Cort. Now
that Cort is "away", we rely mostly on Paul to push patches to Linus.

The latest batch of PPC patches sent by Paul, AFAIK, didn't appear in
Linus test8 (was it rejected ? I don't know)

That's one of the reasons why we have this sourceforge site now. Pleast
post your patches there. They may or may not get merged, but at least
they will be available in a central position and won't be forgotten.

>At the moment, BenH is actively tracking the patches on sourceforge. I
>do jope others will follow his example, and I also hope that more people
>will use sourceforge. Try it out, it's really esay ;-)

Well, a bit less actively for now, I want things to stabilize a bit and
get merged with Linus before feeding the tree with new patches (and I
have my own patches waiting too). Don't worry if you don't see anything
happening on the sourceforge site for the upcoming days, that doesn't
mean it's dead.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-09-12  8:59 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
2000-09-12  8:59         ` Benjamin Herrenschmidt [this message]
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=20000912085918.23901@192.168.1.10 \
    --to=bh40@calva.net \
    --cc=greyham@research.canon.com.au \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    /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).