From: "Michel Dänzer" <michel@daenzer.net>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Harald Welte <laforge@gnumonks.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: linuxppc-2.5 rsync tree broken
Date: 20 Aug 2002 16:44:50 +0200 [thread overview]
Message-ID: <1029854690.691.76.camel@cube> (raw)
In-Reply-To: <20020820143837.GA891@opus.bloom.county>
On Tue, 2002-08-20 at 16:38, Tom Rini wrote:
>
> On Mon, Aug 19, 2002 at 08:01:40PM +0200, Harald Welte wrote:
>
> > The current (at least yesterday and today) linuxppc-2.5 tree at
> > source.mvista.com is broken.
> >
> > It is totally missing the directories sound/core and drivers/usb/core.
>
> What flags are you passing to rsync? Both of those directories exist in
> the tree rsync serves from.
core makes me think of -C alias --cvs-exclude.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-20 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 18:01 linuxppc-2.5 rsync tree broken Harald Welte
2002-08-20 14:38 ` Tom Rini
2002-08-20 14:44 ` Michel Dänzer [this message]
2002-08-20 16:33 ` Harald Welte
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=1029854690.691.76.camel@cube \
--to=michel@daenzer.net \
--cc=laforge@gnumonks.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).