From: iweiny@pacbell•net
To: linuxppc-dev@lists•linuxppc.org (linuxdev)
Subject: Re: Linux/PPC BitKeeper tree announcements
Date: Thu, 18 Jan 2001 17:50:33 -0800 (PST) [thread overview]
Message-ID: <200101190150.RAA01825@batcave2.batcave> (raw)
In-Reply-To: <20010109161126.P18696@hq.fsmlabs.com>
At the risk of sounding stupid I guess I need a newer compiler than egcs for
the new kernel trees?
fork.c:353: fixed or forbidden register 68 (0) was spilled for class CR0_REGS.
This may be due to a compiler bug or to impossible asm
statements or clauses.
Ira
--- To quote Cort Dougan: ---
>
>
> We now have a mailing list for the commit messages for the 2.2 and 2.4
> trees. If you want to keep up on Linux/PPC development take a look at
> http://www.fsmlabs.com/linuxppcbk.html and follow the subscription
> instructions.
>
> I'd like to keep the traffic low on these lists since we have plenty of
> other lists for general discussion. This lists are just for following
> changes to the kernel and some discussion of those changes.
>
> The 2.3 trees are no longer available via anonymous access as they're been
> replaced with a new 2.4 repository. The change was necessary to remove the
> 80MB or so of deleted file (as a result cloning, checking out and committing
> changes is much faster).
>
> For those of you who had work in copies of the 2_3 that you were accessing
> anonymously you need not fear your work is lost. Just generate a diff
> against the last changeset in your repository and reapply it to the 2_4
> tree.
>
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-19 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 23:11 Linux/PPC BitKeeper tree announcements Cort Dougan
2001-01-19 1:50 ` iweiny [this message]
2001-01-19 11:40 ` Franz Sirl
2001-01-19 23:32 ` Kenneth Johansson
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=200101190150.RAA01825@batcave2.batcave \
--to=iweiny@pacbell$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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