linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Chris Boot <bootc@worldnet.fr>
To: LinuxPPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: what is the currently active stable tree?
Date: Fri, 05 Jan 2001 12:28:08 +0100	[thread overview]
Message-ID: <B67B6D1C.7FDF%bootc@worldnet.fr> (raw)
In-Reply-To: <20010105142837.A793@nina.dev.fol>


Hi,

> Just curious where the current stable tree for PPC is?

The released stable tree is at ftp.kernel.org.  If you're looking for a
kernel tree in development, I'm not sure, but check out
http://www.fsmlabs.com/linuxppcbk.html.

Good luck,

--
    .-.        Chris Boot
    /v\     bootc@worldnet.fr
   // \\
  /(   )\   L   I   N   U   X
   ^^-^^   >Phear the Penguin<


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

      reply	other threads:[~2001-01-05 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05  3:28 what is the currently active stable tree? Chris Leishman
2001-01-05 11:28 ` Chris Boot [this message]

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=B67B6D1C.7FDF%bootc@worldnet.fr \
    --to=bootc@worldnet.fr \
    --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).