From: Eric Weikl <eric.weikl@gmx.net>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-devel] [sup-talk] sup: Fix for an UndefinedMethodError
Date: Sun, 14 Apr 2013 13:31:14 +0200 [thread overview]
Message-ID: <1365938152-sup-6420@mint> (raw)
In-Reply-To: <516997BD.7010409@gaute.vetsj.com>
Hi Gaute,
That sounds like a plan of action :-)
Excerpts from Gaute Hope's message of 2013-04-13 19:37:01 +0200:
> - Go for Mail in stead of RMail (index breakage)
Is this related to getting rid of Iconv for Ruby 2.0.0, or is it a
separate issue? Otherwise, I would favor lumping it in the same release
together with IMAP syncback, since both require a migration step by the
user.
> - Integrate the IMAP / label sync back stuff (personally this is what I
> miss the most)
I've been using the imap syncback code by Damien Leone from ezyang's
branch for quite a while now (> 1 year) without any issues. It should be
fairly easy to cherry-pick the relevant commits into the development
branch.
> - Get rid of all dependencies that are abandoned or deprecated (ncurses
> gem..)
+1 I'd also add deleting all unused code and other stuff (server code,
website, Redwood protocol stuff, etc.).
> - Try to do tests on most stuff for different encodings
I thought about adding some functional tests (through the UI or
otherwise), since retrofitting unit tests is probably too much of a pain.
I need to figure out how the parts fit together some more, though.
Do you think that makes sense?
> Would be very nice:
> - Index migration
We could do the index migration like the imap syncback code does - it
recognizes that it wasn't done yet and asks you to run a command-line
tool.
> - Config migration
How exactly will the config change? Possibly it easy to detect via
regular expressions or something?
Cheers,
Eric
next prev parent reply other threads:[~2013-04-14 11:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 18:09 Jonathan Lassoff
2013-04-12 18:46 ` Steven Hum
2013-04-12 19:46 ` Hamish D
2013-04-13 9:16 ` Gaute Hope
2013-04-13 10:09 ` Jonathan Lassoff
2013-04-13 13:17 ` Gaute Hope
2013-04-13 16:35 ` Jonathan Lassoff
2013-04-13 17:14 ` Gaute Hope
2013-04-13 17:37 ` Gaute Hope
2013-04-13 19:19 ` Jonathan Lassoff
2013-04-13 20:48 ` Jonathan Lassoff
2013-04-13 22:17 ` Gaute Hope
2013-04-14 11:31 ` Eric Weikl [this message]
2013-04-14 12:05 ` [sup-devel] " Gaute Hope
2013-04-14 17:39 ` Eric Weikl
2013-04-16 20:30 ` [sup-talk] [sup-devel] " Eric Weikl
2013-04-16 21:21 ` Matthieu Rakotojaona
2013-04-17 8:51 ` Gaute Hope
2013-04-17 3:31 ` Steven Hum
2013-08-15 13:22 ` [sup-devel] Is maildir-sync ready for prime time? Eric Weikl
2013-08-15 13:35 ` [sup-talk] " Steven Schmeiser
2013-04-14 17:45 ` [sup-talk] sup: Fix for an UndefinedMethodError Hamish D
2013-04-14 22:32 ` Gaute Hope
2013-04-15 11:42 ` Gaute Hope
2013-04-13 19:15 ` Jonathan Lassoff
2013-04-13 22:20 ` Gaute Hope
2013-04-13 12:49 ` Matthieu Rakotojaona
2013-04-13 13:29 ` Gaute Hope
2013-04-13 15:42 ` Steven Hum
2013-04-13 10:06 ` Jonathan Lassoff
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=1365938152-sup-6420@mint \
--to=eric.weikl@gmx.net \
--cc=eg@gaute.vetsj.com \
--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