From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Want to contribute to sup
Date: Sat, 15 Jun 2013 17:36:04 +0200 [thread overview]
Message-ID: <1371310273-sup-6422@qwerzila> (raw)
In-Reply-To: <CAE4LD9q+CMMQeqfUwpQ9Dpz=+60dOdvV+Yuu3s+XTAKgwm7OMA@mail.gmail.com>
Excerpts from Anirudh Sanjeev's message of 2013-06-15 16:24:17 +0200:
> I tried using sup in Jan 2010 [1] and used it for a while and was a little
> disheartened when I didn't see a release for a while. Eventually I went
> about using a regular client but I kept checking up on sup.
>
> Today, I discover that the project is active again. And I am a better
> programmer than the last time I tried to work on sup 3 years ago, so I feel
> I can make some meaningful contributions. I will definitely try out the new
> release after I get home.
Great! In case you're not aware of it, also check out the sup-devel list [1].
> I found that the offlineimap/Maildir approach to fetching email resulted in
> emails remaining marked as "unread" on the server and web-clients. Is this
> still the behavior when we use offlineimap to fetch the mail?
The work on syncing back status changes to IMAP (through maildir) is
going on in the maildir-sync branch [2]. It is not yet included in a
release, but it will hopefully soon be ready. Usage instructions [3] and
some development notes [4] are available in the wiki.
Regards, Gaute
[1] http://rubyforge.org/pipermail/sup-devel/
[2] https://github.com/sup-heliotrope/sup/tree/maildir-sync
[3] https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
[4] https://github.com/sup-heliotrope/sup/wiki/Development%3A-Maildir-syncback
prev parent reply other threads:[~2013-06-15 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 14:24 Anirudh Sanjeev
2013-06-15 15:36 ` Gaute Hope [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=1371310273-sup-6422@qwerzila \
--to=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