From: Paul Mackerras <paulus@linuxcare.com>
To: howarth@bromo.med.uc.edu (Jack Howarth), linuxppc-dev@lists.linuxppc.org
Subject: Re: linux-pmac-devel
Date: Mon, 14 Feb 2000 13:43:50 +1100 [thread overview]
Message-ID: <00021413444901.00486@argo.linuxcare.com.au> (raw)
In-Reply-To: 200002140006.QAA49713@bromo.med.uc.edu
On Mon, 14 Feb 2000, Jack Howarth wrote:
> I think there is error somewhere in the config scripts in the 2.3.xx
> tree. When I rsync, do a make clean and then make config I get...
I just updated the tree to 2.3.45-pre2, maybe you were rsyncing out of it
while I was updating it? Try rsyncing again and see if it still happens.
--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare. Support for the revolution.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-02-14 2:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200002140006.QAA49713@bromo.med.uc.edu>
2000-02-14 2:43 ` Paul Mackerras [this message]
2000-02-14 5:16 ` linux-pmac-devel Brad Midgley
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=00021413444901.00486@argo.linuxcare.com.au \
--to=paulus@linuxcare.com \
--cc=howarth@bromo.med.uc.edu \
--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).