From: Paul Mackerras <paulus@linuxcare.com>
To: Linux/PPC Developer list <linuxppc-dev@lists.linuxppc.org>
Subject: my rsync trees
Date: Fri, 26 Nov 1999 16:05:13 +1100 [thread overview]
Message-ID: <99112616173402.00490@argo.linuxcare.com.au> (raw)
Those of you who were having trouble using rsync -z with the rsync trees at
linuxcare.com.au should try again. The trouble was that that is a Debian
system and the latest debian rsync package got installed. Some clever
debian maintainer decided that rsync should use the standard zlib, instead
of the extended zlib that comes with rsync. :-)
Currently linuxcare.com.au::linux-pmac-stable is at 2.2.14-pre9, and
linux-pmac-devel is at 2.3.29. There is a precompiled 2.2.14pre9 kernel
in ftp://linuxcare.com.au/pub/ppclinux/kernels/2.2.14p9/.
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~1999-11-26 5:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=99112616173402.00490@argo.linuxcare.com.au \
--to=paulus@linuxcare.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;
as well as URLs for NNTP newsgroup(s).