From: Tom Rini <trini@kernel.crashing.org>
To: Allen Curtis <acurtis@onz.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: rsync linuxppc-2.5?
Date: Mon, 13 May 2002 10:05:31 -0700 [thread overview]
Message-ID: <20020513170531.GF721@opus.bloom.county> (raw)
In-Reply-To: <NCBBIINEHIPFGJPLBEIFCEPDDGAA.acurtis@onz.com>
On Mon, May 13, 2002 at 08:02:00AM -0700, Allen Curtis wrote:
> While trying to rsync linuxppc-2.5, I get an error saying that chroot
> failed...connection unexpectently closed.
Whoops, typo in the conf file. This is fixed now.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-05-13 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 15:02 rsync linuxppc-2.5? Allen Curtis
2002-05-13 17:05 ` Tom Rini [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=20020513170531.GF721@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=acurtis@onz.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