From: Steven Hum <sdothum@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
Date: Tue, 16 Apr 2013 23:31:33 -0400 [thread overview]
Message-ID: <1366169414-sup-1740@luna> (raw)
In-Reply-To: <1366143381-sup-8459@mint>
Beautiful! I will begin using this in place of my copy of ezyang's fork
immediately.
Thanks for all your hard work,
Steven
Excerpts from Eric Weikl's message of 2013-04-16 16:30:26 -0400:
> Hi everyone,
>
> I created a new branch with all the commits from Damien Leone and Edward
> Yang related to maildir syncback and put it here:
>
> https://github.com/sup-heliotrope/sup/tree/maildir-sync
>
> I skipped some advanced stuff like Edward's inotify support for now. We
> can add that later.
>
> I performed some basic testing, but it would be great if some more people
> could give it a try. There's some documentation in the wiki:
>
> https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
>
> Cheers,
> Eric
>
> Excerpts from Gaute Hope's message of 2013-04-14 14:05:52 +0200:
> > Cool. I would really like to see this in main sup, any other
> > objections? In my view the main arguments are:
> >
> > - Manipulating IMAP could mess up user mail (potentially new bugs could
> > mess up)
> > - Maintaining this functionality requires some long-term (at least
> > minor) effort
> > - It modifies the mail store (could be solved with disabled-by-default)
> > which I think is a big plus for many
> >
> > I would suggest creating a official branch for this now, if you are
> > interested I could add you as commiter or owner.
--
"Truth or die."
Steven Hum
5 - 28 Gilmour St
Ottawa, ON K2P 0N3
email sdothum@gmail.com
tel 613.237.9058
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2013-04-17 4:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 18:09 [sup-talk] " 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 ` [sup-devel] " Eric Weikl
2013-04-14 12:05 ` 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 [this message]
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=1366169414-sup-1740@luna \
--to=sdothum@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