From: Tom Rini <trini@kernel.crashing.org>
To: John Tyner <jtyner@cs.ucr.edu>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: cannot get tree with rsync
Date: Tue, 5 Feb 2002 16:14:36 -0700 [thread overview]
Message-ID: <20020205231436.GV32707@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.30.0202050934260.5889-100000@hill.cs.ucr.edu>
On Tue, Feb 05, 2002 at 09:40:29AM -0800, John Tyner wrote:
> Is anyone else having problems getting the linuxppc_2_4_devel tree from
> source.mvista.com.
Can you re-try this now? I just upgraded rsync on the machine.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-05 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 17:40 cannot get tree with rsync John Tyner
2002-02-05 23:14 ` Tom Rini [this message]
2002-02-06 0:18 ` John Tyner
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=20020205231436.GV32707@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=jtyner@cs.ucr.edu \
--cc=linuxppc-embedded@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.