linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@cgsoftware.com>
To: "Joseph P. Garcia" <jpgarcia@execpc.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: aty128fb.c missing from rync'd benh sources...
Date: Fri, 27 Jul 2001 01:26:43 -0400	[thread overview]
Message-ID: <87ae1rx7qk.fsf@cgsoftware.com> (raw)
In-Reply-To: <20010726212643.31b93eeb.jpgarcia@execpc.com> ("Joseph P. Garcia"'s message of "Thu, 26 Jul 2001 21:26:43 -0500")


"Joseph P. Garcia" <jpgarcia@execpc.com> writes:

> On Thu, 26 Jul 2001 21:08:32 -0400
> Daniel Berlin <dan@cgsoftware.com> wrote:
>> You just aren't using the --delete flag, so it never deleted the file.
>
> Confirmed.  Just ran a sync.
>
> ...
> deleting toto
> deleting fs/cramfs/cramfs.h
> deleting drivers/video/aty128fb.c
> deleting drivers/ieee1394/guid.h
> deleting drivers/ieee1394/guid.c
> deleting drivers/ieee1394/aic5800.h
> deleting drivers/ieee1394/aic5800.c
> ...
>
> And rsync will only delete files if run with the --delete flag.


Right. Mirrors with extra space will keep older, deleted, versions of files
around (remember, rsync is a mirroring tool), while those with less
space will just want an exact mirror (or whatever). Hence the
--max-delete flag, and whatnot.




>
> --
> Joseph P. Garcia
> http://www.lycestra.com/
>

--
"I didn't get a toy train like the other kids.  I got a toy
subway instead.  You couldn't see anything, but every now and
then you'd hear this rumbling noise go by.
"-Steven Wright

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-07-27  5:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-27  0:07 aty128fb.c missing from rync'd benh sources Armando Di Cianno
2001-07-27  0:09 ` Ethan Blanton
2001-07-27  0:44   ` Armando Di Cianno
2001-07-27  0:36     ` Larry McVoy
2001-07-27  0:53       ` Armando Di Cianno
2001-07-27  1:08   ` Daniel Berlin
2001-07-27  2:26     ` Joseph P. Garcia
2001-07-27  5:26       ` Daniel Berlin [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=87ae1rx7qk.fsf@cgsoftware.com \
    --to=dan@cgsoftware.com \
    --cc=jpgarcia@execpc.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).