From: David Ford <david+challenge-response@blue-labs.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Jim Nelson <james4765@verizon.net>,
Kurt Wall <kwall@kurtwerks.com>,
linux-kernel@vger.kernel.org, pj@sgi.com
Subject: Re: mozilla-mail damage [was Re: [PATCH] Update to Documentation/ramdisk.txt - take 2]
Date: Sat, 23 Oct 2004 15:56:16 -0400 [thread overview]
Message-ID: <417AB760.3090007@blue-labs.org> (raw)
In-Reply-To: <1098505741.13176.11.camel@krustophenia.net>
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
just do one of:
1> drag into attachments window
2> paste as text and format plain
3> send as plain text email unwrapped
-david
Lee Revell wrote:
>On Sat, 2004-10-23 at 00:18 -0400, Jim Nelson wrote:
>
>
>>Probably need to make using Paul Jackson's sendpatchset script de riguer
>>recommendation for GUI mail client users
>>
>>
>
>Nope, just Mozilla. Evolution does the Right Thing - it handles the X
>clipboard correctly AND has a menu item to "insert text file".
>
>Lee
>
>
>
[-- Attachment #2: david+challenge-response.vcf --]
[-- Type: text/x-vcard, Size: 183 bytes --]
begin:vcard
fn:David Ford
n:Ford;David
email;internet:david@blue-labs.org
title:Industrial Geek
tel;home:Ask please
tel;cell:(203) 650-3611
x-mozilla-html:TRUE
version:2.1
end:vcard
next prev parent reply other threads:[~2004-10-23 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 1:45 [PATCH] Update to Documentation/ramdisk.txt - take 2 Jim Nelson
2004-10-23 2:12 ` Kurt Wall
2004-10-23 2:35 ` Lee Revell
2004-10-23 3:16 ` mozilla-mail damage [was Re: [PATCH] Update to Documentation/ramdisk.txt - take 2] Lee Revell
2004-10-23 4:18 ` Jim Nelson
2004-10-23 4:29 ` Lee Revell
2004-10-23 5:29 ` Con Kolivas
2004-10-23 19:56 ` David Ford [this message]
2004-10-23 20:11 ` Lee Revell
2004-10-23 7:42 ` Paul Jackson
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=417AB760.3090007@blue-labs.org \
--to=david+challenge-response@blue-labs.org \
--cc=james4765@verizon.net \
--cc=kwall@kurtwerks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=rlrevell@joe-job.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