From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] sup failing to display the text of a message
Date: Tue, 10 Jul 2007 13:40:39 -0400 [thread overview]
Message-ID: <1184088645-sup-8679@mona> (raw)
In-Reply-To: <1184081531-sup-3358@south>
Excerpts from William Morgan's message of Tue Jul 10 11:45:38 -0400 2007:
> So I could patch RubyMail (which is completely unmaintained, so I'd
> essentially have to publish the patch in parallel with Sup) to handle
> these messages, which is dubious by the RFCs but probably fine in
> practice, or I could just ignore the issue as "someone else's problem".
> Since the message content is still viewable in Sup, I'm tempted to leave
> things as is.
ok, thanks for checking into it!
--
jeff covey
http://jeffcovey.net/
prev parent reply other threads:[~2007-07-10 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 1:30 jeff covey
2007-07-07 12:17 ` jeff covey
2007-07-08 15:44 ` William Morgan
2007-07-09 14:44 ` jeff covey
2007-07-10 15:45 ` William Morgan
2007-07-10 17:40 ` jeff covey [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=1184088645-sup-8679@mona \
--to=jeff.covey@pobox.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