From: Paul Nasrat <pauln@truemesh.com>
To: linux-8086@vger.kernel.org
Subject: Re: Whoops!!
Date: Tue, 2 Mar 2004 11:46:27 +0000 [thread overview]
Message-ID: <20040302114620.GD11498@lichen.truemesh.com> (raw)
In-Reply-To: <20040229165339.62270.qmail@web11703.mail.yahoo.com>
On Sun, Feb 29, 2004 at 08:53:39AM -0800, Tommy McCabe wrote:
> I forgot to attach the files before pressing the
> 'Send' button! Sorry.
Thanks for these. I'll try and spend some time this week to look at them.
Paul
next prev parent reply other threads:[~2004-03-02 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 16:53 Whoops!! Tommy McCabe
2004-03-02 11:46 ` Paul Nasrat [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-13 13:18 Whoops! Tommy McCabe
2004-07-27 13:54 ` Whoops! Miguel Bolanos
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=20040302114620.GD11498@lichen.truemesh.com \
--to=pauln@truemesh.com \
--cc=linux-8086@vger.kernel.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