From: anonymous <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue133] add support for the mh mailbox format
Date: Sat, 27 Nov 2010 11:15:50 +0000 [thread overview]
Message-ID: <1290856550.06.0.787394879314.issue133@masanjin.net> (raw)
In-Reply-To: <1290856550.06.0.787394879314.issue133@masanjin.net>
New submission from anonymous:
I've been using the mh format (via nmh) for years, and it would be fantastic if
sup could support it so people don't have to convert mailboxes to maildir or mbox
to be able to use sup.
----------
messages: 312
nosy: anonymous
priority: feature request
ruby_version: 1.8
status: unread
sup_version: 0.11
title: add support for the mh mailbox format
_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue133>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next parent reply other threads:[~2010-11-27 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 11:15 anonymous [this message]
2010-11-30 13:01 ` Nicolas Pouillard
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=1290856550.06.0.787394879314.issue133@masanjin.net \
--to=sup-bugs@masanjin.net \
--cc=sup-devel@rubyforge.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