Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Anirudh Sanjeev <skyronic@gmail.com>
To: sup-talk@rubyforge.org
Subject: [sup-talk] Want to contribute to sup
Date: Sat, 15 Jun 2013 19:54:17 +0530	[thread overview]
Message-ID: <CAE4LD9q+CMMQeqfUwpQ9Dpz=+60dOdvV+Yuu3s+XTAKgwm7OMA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 829 bytes --]

Hi,

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.

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?

Thank you,
Anirudh


[1]: http://rubyforge.org/pipermail/sup-talk/2010-January/003726.html

-- 
Co-founder and Developer, RazorFlow
http://razorflow.com

[-- Attachment #1.2: Type: text/html, Size: 1269 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

             reply	other threads:[~2013-06-15 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15 14:24 Anirudh Sanjeev [this message]
2013-06-15 15:36 ` 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='CAE4LD9q+CMMQeqfUwpQ9Dpz=+60dOdvV+Yuu3s+XTAKgwm7OMA@mail.gmail.com' \
    --to=skyronic@gmail.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