Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Steven Schmeiser <steven@schmeiser.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Is maildir-sync ready for prime time?
Date: Thu, 15 Aug 2013 09:35:17 -0400	[thread overview]
Message-ID: <1376573604-sup-1651@indy.local> (raw)
In-Reply-To: <1376572537-sup-83@mint>


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

I've been using the maildir-sync branch for a month or so and have not encountered any problems.  I also vote for a merge.

Steve
 
> Hi fellow sup users,
> 
> the maildir-sync branch has been hanging around for quite a while. Since
> sup 0.14.0 is out now, we could consider merging it into the developer
> branch. I've been using the branch continuously and haven't encountered
> any problems so far.
> 
> Has anyone else tried the branch, or is willing to do so? It would be
> great to have some more opinions on it.
> 
> Gaute created a corresponding pull request here:
> https://github.com/sup-heliotrope/sup/pull/126
> 
> Cheers,
> Eric
> 
> On 04/16/2013 22:30:26, Eric Weikl wrote:
> > 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

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 841 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-08-15 13:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 18:09 [sup-talk] sup: Fix for an UndefinedMethodError 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
2013-08-15 13:22                     ` [sup-devel] Is maildir-sync ready for prime time? Eric Weikl
2013-08-15 13:35                       ` Steven Schmeiser [this message]
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=1376573604-sup-1651@indy.local \
    --to=steven@schmeiser.org \
    --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