From: Michael Cook <cook@nexthop.com>
Subject: Re: flow-fill.el and rfc3676
Date: Mon, 17 Apr 2006 11:43:15 -0400 [thread overview]
Message-ID: <m3d5fgnr70.fsf@pigpen.waxrat.com> (raw)
In-Reply-To: <m364l8o9ch.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 17 Apr 2006 11:11:10 +0200")
[-- Attachment #1: Type: text/plain, Size: 420 bytes --]
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Michael Cook <michael@waxrat.com> writes:
>
>>> Sure. Could you forward a message that uses delsp?
>>
>> see attached. i can provide more if you want. fwiw, it seems to be
>> an Apple application that generates 3676.
>
> I didn't see any delsp in that message...
hmm, something transformed the message...
here it is a again, this time attached as a gzipped file.
[-- Attachment #2: 2038.gz --]
[-- Type: application/x-gzip, Size: 4562 bytes --]
next prev parent reply other threads:[~2006-04-17 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 17:23 Michael Cook
2006-04-16 15:20 ` Lars Magne Ingebrigtsen
2006-04-17 2:29 ` Michael Cook
2006-04-17 9:11 ` Lars Magne Ingebrigtsen
2006-04-17 15:43 ` Michael Cook [this message]
2006-04-18 16:52 ` Lars Magne Ingebrigtsen
2006-04-18 8:45 ` Simon Josefsson
2006-04-18 16:31 ` Lars Magne Ingebrigtsen
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=m3d5fgnr70.fsf@pigpen.waxrat.com \
--to=cook@nexthop.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).