mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: tom_gall@vnet.ibm.com
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: PowerPC branch out of date
Date: Fri, 29 Dec 2000 15:11:57 +0000	[thread overview]
Message-ID: <3A4CA9BD.E8E4D6E1@vnet.ibm.com> (raw)

Hi Linus,

  I'm one of the folks that works on the PowerPC portion of the kernel. I've
noticed for some time that what's available at kernel.org and what's being
worked on by those of us who maintain our little portion of the PowerPC tree is
more and more out of sync. 
  How it's got there etc etc etc at this stage isn't important. First how to fix
it and how to make sure it doesn't happen again does concern me.
  
  Currently the diff between test13-preX and the master fsmlabs.com ppc tree is
about 450k. Is the right thing to start with that patch get that into the
test13-preX series?

  I would REALLY appreciate it if this could be made to happen. I've got a whole
boatload of RS/6000 (aka pSeries) hardware that will be starting to work once
this patch is in. It's truely a shame to have to explain to people that
kernel.org *SHOULD* be the place to get a good kernel but given that things are
out of sync to have to point them somewhere else.
  
  Regards,

  Tom

-- 
Tom Gall - PowerPC Linux Team    "Where's the ka-boom? There was
Linux Technology Center           supposed to be an earth
(w) tom_gall@vnet.ibm.com         shattering ka-boom!"
(w) 507-253-4558                 -- Marvin Martian
(h) tgall@rochcivictheatre.org
http://oss.software.ibm.com/developerworks/opensource/linux
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-29 15:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-29 15:11 tom_gall [this message]
2000-12-29 16:40 ` Rik van Riel
2000-12-29 17:25   ` Tom Rini

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=3A4CA9BD.E8E4D6E1@vnet.ibm.com \
    --to=tom_gall@vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®