From: Dan Malek <dan@embeddededge.com>
To: Jim Thompson <jim@musenki.com>
Cc: Adrian Cox <adrian@humboldt.co.uk>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPC107 I2C
Date: Fri, 08 Feb 2002 15:50:06 -0500 [thread overview]
Message-ID: <3C6439FE.3040408@embeddededge.com> (raw)
In-Reply-To: 15460.13505.638556.964526@gargle.gargle.HOWL
Jim Thompson wrote:
> OK, but thats now how I meant it. I hadn't seen my email come back
> from either list.
I guess I didn't use enough of these :-) :-).
I have noticed that sometimes my messages take a long time to appear
and other times they are almost instant, so I kind of understand your
asking.
Have a good one.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-08 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 9:40 MPC107 I2C Adrian Cox
2002-02-08 15:58 ` Dan Malek
2002-02-08 16:23 ` Adrian Cox
2002-02-08 16:40 ` Jim Thompson
2002-02-08 16:47 ` Dan Malek
2002-02-08 20:27 ` Jim Thompson
2002-02-08 20:50 ` Dan Malek [this message]
2002-02-08 17:46 ` Adrian Cox
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=3C6439FE.3040408@embeddededge.com \
--to=dan@embeddededge.com \
--cc=adrian@humboldt.co.uk \
--cc=jim@musenki.com \
--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 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).