From: Jeff Garzik <jgarzik@pobox.com>
To: "Winstel, Drew" <DWinstel@Miltope.com>
Cc: "Linux-Ide (E-mail)" <linux-ide@vger.kernel.org>
Subject: Re: resend: attachment from previous message
Date: Tue, 22 Feb 2005 16:58:14 -0500 [thread overview]
Message-ID: <421BAAF6.50905@pobox.com> (raw)
In-Reply-To: <66F9227F7417874C8DB3CEB057727417044F9A@MILEX0.Miltope.local>
Winstel, Drew wrote:
> My apologies go out to anyone whose email server
> rejected my previous email due to my attachment not
> having an extension.
That's a broken mail server. Resending _correct_ emails just clogs up
the mail archives and sends everyone a duplicate message.
The Linux kernel community sends out emails with file "patch" (no
extension) attached all the time.
Jeff
prev parent reply other threads:[~2005-02-22 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 21:27 resend: attachment from previous message Winstel, Drew
2005-02-22 21:58 ` Jeff Garzik [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=421BAAF6.50905@pobox.com \
--to=jgarzik@pobox.com \
--cc=DWinstel@Miltope.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).