From: Shadowfirebird <shadowfirebird@gmail.com>
To: Rich Lane <rlane@club.cc.cmu.edu>
Cc: sup-talk <sup-talk@rubyforge.org>,
sup-devel <sup-devel@rubyforge.org>,
sup-announce <sup-announce@rubyforge.org>
Subject: Re: [sup-talk] Sup 0.12 released
Date: Mon, 17 Jan 2011 10:44:42 +0000 [thread overview]
Message-ID: <AANLkTimE-40sx8xXxQbjz=Jok3FnWJZgmNTBiMObRahx@mail.gmail.com> (raw)
In-Reply-To: <1295068347-sup-3453@zyrg.net>
[-- Attachment #1.1: Type: text/plain, Size: 1965 bytes --]
That's nice.
Can I make a criticism? Perhaps there should have been a warning that
upgrading is not just a matter of running "gem upgrade sup" because there
are engine changes, with a link to the detailed description on the web of
how to upgrade?
And perhaps you should put a detailed descrption on the web of how to
upgrade?
"This Sup version expects a v4 index, but you have an existing v2 index.
Please run sup-dump to save your labels, move /home/fred/.sup/xapian out of
the way, and run sup-sync --restore."
Perhaps it really is as simple as this, but this is my "live" data we are
talking about here. A little hand-holding would not have gone amis.
On Sat, Jan 15, 2011 at 7:07 AM, Rich Lane <rlane@club.cc.cmu.edu> wrote:
> I'm pleased to announce the release of Sup 0.12.
>
> Sup is a console-based email client for people with a lot of email.
> It supports tagging, very fast full-text search, automatic contact-
> list management, and more. If you're the type of person who treats
> email as an extension of your long-term memory, Sup is for you.
>
> Get it: gem install sup
> Learn it: http://sup.rubyforge.org
> Love it: sup-talk@rubyforge.org
>
> Release notes:
>
> Deprecated remote sources have been removed.
>
> Maildir support has been improved to gracefully handle messages that
> move or disappear. The "out of sync" errors should no longer occur.
>
> Inline GPG is now supported.
>
> Changelog for 0.12:
>
> * Remove deprecated IMAP, IMAPS, and mbox+ssh sources
> * Inline GPG support
> * Robust maildir support
> * sup-dump compatibility between Sup versions
> * New hook: sendmail
> * Better Ruby 1.9/UTF8 support
> * As always, many bugfixes and tweaks.
> _______________________________________________
> sup-talk mailing list
> sup-talk@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
>
--
What a tangled web we weave / Go 'round with circumstance / Someone show me
how to tell / The dancer from the dance...
[-- Attachment #1.2: Type: text/html, Size: 2664 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-01-17 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 7:07 [sup-devel] " Rich Lane
2011-01-17 10:44 ` Shadowfirebird [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='AANLkTimE-40sx8xXxQbjz=Jok3FnWJZgmNTBiMObRahx@mail.gmail.com' \
--to=shadowfirebird@gmail.com \
--cc=rlane@club.cc.cmu.edu \
--cc=sup-announce@rubyforge.org \
--cc=sup-devel@rubyforge.org \
--cc=sup-talk@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