linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Costabel <costabel@wanadoo.fr>
To: Sriranga Veeraraghavan <ranga@CSUA.Berkeley.EDU>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: cvs kernel does not compile
Date: Thu, 13 May 1999 23:59:30 +0200	[thread overview]
Message-ID: <373B4B42.D315FF4C@wanadoo.fr> (raw)
In-Reply-To: 199905131906.MAA17049@soda.CSUA.Berkeley.EDU


Sriranga Veeraraghavan wrote:
> 
> > Well.  2.3.0 is 2.2.8.  2.3.1-pre2 (in CVS now) is not. :)
> 
> This may be a stupid question, but what is the best site to download
> the latest version of the kernel with the current PPC/PMac fixes?
> 
> I haven't had very good luck with the kernel src on linuxhq.com.

If you are on cvs from openprojects, you can get a 2.3.0 kernel via
 cvs -z3 update -D "5/12/99 10:00:00"
This is more or less the latest one that actually compiles.

But since the linuxppc developers release 1.0 is out now, the 2.2.6-15a
kernel sources that come with it will probably remain a stable reference
for some time to come.

--
Martin

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-05-13 21:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-12 14:08 cvs kernel does not compile Konstantinos Margaritis
1999-05-12 19:40 ` Tom Rini
1999-05-12 21:31   ` Martin Costabel
1999-05-12 21:37     ` Tom Rini
1999-05-13 11:57       ` Martin Costabel
1999-05-13 19:06       ` Sriranga Veeraraghavan
1999-05-13 21:59         ` Martin Costabel [this message]
1999-05-13 22:12         ` 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=373B4B42.D315FF4C@wanadoo.fr \
    --to=costabel@wanadoo.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=ranga@CSUA.Berkeley.EDU \
    /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).