From: Gaute Hope <eg@gaute.vetsj.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: sup for 2.0
Date: Sat, 11 May 2013 12:38:16 +0200 [thread overview]
Message-ID: <518E1F98.5070308@gaute.vetsj.com> (raw)
Greetings suppers,
I was thinking about setting up a branch for next generation sup, I have
partly switched to Mail (in stead of RMail) and started migrating to
using safe-ids in the index as opposed to the slightly modified
message-id and message-refs. I have put this in a sup-for-two branch
[1]. It is based on the discussion in issue 22 [2].
Anyway, my proposal is: we set up a sup-for-two branch on origin. The
things that should go in there are:
- maildir-sync
- Mail
- Id -> safe id change
- other big changes we want for sup-0.14 or the future
The only mature feature here is the maildir-sync branch (which I have
also based my Mail work on). I still think that we should merge in the
Mail work pretty soon because the change of id to safeid (also for all
refs) will be extra work to port later - given that we move to Mail.
There are some issues and unfinished things still:
- performance (about half of RMail)
- only implemented for maildir, not for mbox or for sending
- haven't figured out all threading logic [3]
- migration script for index [4] is incomplete (and it might not even be
really possible)
Mail is UTF-8 (but crashes on too nasty input [5]), I've started to
collect nasty emails for testing purposes.. we should add those to the
test-suite somehow. So far most UTF-8 issues seems to have been solved
by [6] and native UTF-8 in Mail. Tested on some 25k of email of
extremely varying quality.
Comments are appreciated.
Regards, Gaute
[1] https://github.com/gauteh/sup/tree/sup-for-two
[2] https://github.com/sup-heliotrope/sup/issues/22
[3] https://github.com/gauteh/sup/blob/sup-for-two/lib/sup/thread.rb#L299
[4] https://github.com/gauteh/sup/blob/sup-for-two/bin/sup-migrate-index
[5] https://github.com/mikel/mail/issues/544
[6] https://github.com/gauteh/sup/blob/sup-for-two/lib/sup/util.rb#L344
reply other threads:[~2013-05-11 10:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=518E1F98.5070308@gaute.vetsj.com \
--to=eg@gaute.vetsj.com \
--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