All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@cgsoftware.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: aty128fb.c missing from rync'd benh sources...
Date: Thu, 26 Jul 2001 21:08:32 -0400	[thread overview]
Message-ID: <87elr3xjov.fsf@cgsoftware.com> (raw)
In-Reply-To: <20010726200901.C8790@localhost.localdomain> (Ethan Blanton's message of "Thu, 26 Jul 2001 20:09:01 -0400")


Ethan Blanton <eblanton@cs.ohiou.edu> writes:

> Armando Di Cianno spake unto us the following wisdom:
>> I did an rsync to penguinppc.org::linux-2.4-benh at approx 7/26/01 8 PM
>> EST.
>
> I just rsync'd (8:07PM EST) and it's there.

No, he's right, you are wrong.
You just aren't using the --delete flag, so it never deleted the file.

>
>> 'make vmlinux' fails in the video directory complaing it is not able to
>> find aty128fb.o.  I checked in drivers/video and there is no aty128fb.c
>> file anymore; I re-rsynced to make sure it wasn't my incompetence.
>>
>> Since the benh kernel tends to be my 'favorite', I'd like to get my TiBook
>> re-rsynced whenever possible.  Is there any reason this file was removed,
>> or was it a mistake?
>
> Ethan
>
> --
> If I've told you once, I've told you once
> And once is all that you needed.
> 		-- The Refreshments, "Carefree"

--
"I was in the grocery store.  I saw a sign that said "pet
supplies."  So I did.  Then I went outside and saw a sign that
said "compact cars"...
"-Steven Wright

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

  parent reply	other threads:[~2001-07-27  1:08 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 [this message]
2001-07-27  2:26     ` Joseph P. Garcia
2001-07-27  5:26       ` Daniel Berlin

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=87elr3xjov.fsf@cgsoftware.com \
    --to=dan@cgsoftware.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 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.