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.le...@fensalir.fr> GPG: 0x82EB4DDF _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
