From: Dan Malek <dmalek@jlc.net>
To: Michael Thompson <mickey@berkeley.innomedia.com>
Cc: Olivier DERVYN <dervyn@digigram.com>,
Linux PPC Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Linux PPC on Sandpoint or YellowKnife board with 750
Date: Fri, 04 Feb 2000 02:34:28 -0500 [thread overview]
Message-ID: <389A8104.AC2C196D@jlc.net> (raw)
In-Reply-To: 200002031505.HAA04494@berkeley.innomedia.com
Michael Thompson wrote:
> ...... I still have
> the patches if anyone wants them, of course.
Of course we want them. Where were you for the past six months
when we would discuss the Sandpoint :-)? You are now the third person
that has duplicated work by the rest of us. Let's stop that from
happening.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-04 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-03 9:06 Linux PPC on Sandpoint or YellowKnife board with 750 Olivier DERVYN
2000-02-03 15:05 ` Michael Thompson
2000-02-04 7:34 ` Dan Malek [this message]
2000-02-04 8:27 ` Olivier DERVYN
2000-02-05 0:45 ` Dan Malek
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=389A8104.AC2C196D@jlc.net \
--to=dmalek@jlc.net \
--cc=dervyn@digigram.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mickey@berkeley.innomedia.com \
/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).