LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: linuxppc <linuxppc@4bridgeworks.com>
To: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Kernel versions
Date: Fri, 2 Jul 2004 14:11:31 +0100	[thread overview]
Message-ID: <C18BA5DDB58DD511BD0700C0DF0DD450294191@NTSERVER4> (raw)


Is there a linuxppc-2.6 kernel tree or are they still using the linuxppc-2.5
tree?

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

             reply	other threads:[~2004-07-02 13:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02 13:11 linuxppc [this message]
2004-07-02 14:29 ` Kernel versions Giuliano Pochini
2004-07-02 14:54   ` Wolfgang Denk
2004-07-02 15:37     ` Giuliano Pochini
2004-07-02 15:56     ` Gary Thomas
2004-07-06 15:08       ` Benjamin Herrenschmidt
2004-08-13 16:59         ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2017-03-08 20:52 kernel versions Tobin C. Harding
2017-03-09 23:48 ` Daniel Axtens
2003-10-02 12:17 Queston about Walnut Wolfgang Denk
2003-10-03  1:18 ` Jacky Lam
     [not found]   ` <3F7D3238.2090400@bluewin.ch>
     [not found]     ` <20031003151729.GC21468@ip68-0-152-218.tc.ph.cox.net>
2003-10-03 23:36       ` Kernel versions Gary Thomas
2003-10-07 13:37         ` 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=C18BA5DDB58DD511BD0700C0DF0DD450294191@NTSERVER4 \
    --to=linuxppc@4bridgeworks.com \
    --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