From: Damien Leone <damien.leone@fensalir.fr>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Maildir support
Date: Tue, 12 Apr 2011 09:34:45 +0200 [thread overview]
Message-ID: <1302593225-sup-1657@mailer> (raw)
In-Reply-To: <1302557683-sup-109@minibox>
Hi,
Excerpts from dtk's message of lun. avril 11 23:44:51 +0200 2011:
> why is that? I thought the way a MUA is supposed to work with a maildir is
> rather straight forward[0]?
Well, yeah, but not sup. :)
> Thanks for the hint!!
> I am a bit suspicious, though :| I don't know much about git, but doesn't that
> essentially mean that the branch is always stuck behind the features in master
> until the new features have manually been merged in?
> And that for every release of master a manual release of the 'maildir' branch
> has to be made?
I keep the maildir-sync branch up to date. If you want the latest
version of sup and the maildir synchronization support then use the
branch maildir-sync-next from my repository.
> Additionally, I consider this a very basic feature. What happens, if there is
> another basic feature that is maintained in _another_ branch? How will I ever be
> able to use them together?
Other features usually get merged faster.
> You know, I'm just wondering why this feature isn't merged in upstream. Are
> there any reasons why anyone would _not_ want proper maildir handling? Or is this
> just a political decision (scared, since I've seen a few of those pull down cool
> projects :/)?
I think it will be merged for the next version although I didn't have
any confirmation from William yet. I don't see any reason why that
wouldn't be the case, as you said there are a lot of people interested
in this feature.
The reason why it is not merged yet is that the code has been finished
a few weeks ago and needs some more testing (even if I've been using
it for 9 months without trouble as well as other people from this
list).
--
Damien Leone <damien.leone@fensalir.fr>
GPG: 0x82EB4DDF
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-04-12 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 8:08 dtk
2011-04-11 9:22 ` Damien Leone
2011-04-11 21:44 ` dtk
2011-04-12 7:34 ` Damien Leone [this message]
2011-04-12 20:41 ` dtk
2011-04-12 21:43 ` Matthieu Rakotojaona
2011-04-12 22:18 ` dtk
2011-04-11 13:05 ` Ruthard Baudach
2011-04-11 21:58 ` dtk
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=1302593225-sup-1657@mailer \
--to=damien.leone@fensalir.fr \
--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