From: Per Andersson <avtobiff@gmail.com>
To: supmua@googlegroups.com
Subject: Sup in Debian
Date: Mon, 25 Aug 2014 23:34:03 +0200 [thread overview]
Message-ID: <CABYrXSTBZC2-ce9RO+ui0W3eSaZOGi3Np-0493WRxoGvnqM+=w@mail.gmail.com> (raw)
Hi!
I am the maintainer for the Sup package in Debian, sup-mail.
There are a few open questions which, together with lack of
time, have ended up in the situation where sup-mail was
removed from Debian.
I want to reintroduce it of course.
The questions:
I can't find if rmail and rmail-sup have merged upstream.
Is there any activity in 1) original rmail, 2) migration away
from rmail?
What are the difference between rmail and rmail-sup?
(I am thinking that maybe the Debian package should switch
upstream source from rmail to rmail-sup.)
The last package in Debian (stable) is 0.12.1, what is the
migration path to current release, 0.19.0?
--
Per
next reply other threads:[~2014-08-25 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 21:34 Per Andersson [this message]
2014-08-26 8:34 ` [sup] " Gaute Hope
2014-09-02 15:05 ` Caitlin Matos
2014-09-03 7:30 ` Gaute Hope
2014-10-02 6:17 ` Per Andersson
2014-10-02 15:23 ` Gaute Hope
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='CABYrXSTBZC2-ce9RO+ui0W3eSaZOGi3Np-0493WRxoGvnqM+=w@mail.gmail.com' \
--to=avtobiff@gmail.com \
--cc=supmua@googlegroups.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