On 09/05/2013 07:17 PM, Lynn Dobbs wrote:
> What is the reason that the master branch has files named like dm_*.c
> but in the stable tarball some are renamed dbmail-*.c? I was just trying
I renamed some files to make things more consistent. No other reason,
just me gold-plating.
> to apply the very latest patches and discovered I can't use them to
> patch the 3.1.5 release. I'm assuming it is intentional.
You can, but you need to use 'git cherry-pick', which is what I use
constantly to apply patches to-and-fro the master branch.
cherry-pick is *very* good at tracking stuff like file-renames, and
conflict resolution. Generic 'patch' doesn't come close by any measure.
But what patches would you want to apply? If there are things from the
master branch, you better run the master branch. It's 3.1 plus some new
features (imap capabilities, schema auto-migration, security password)
and the results of my first security audit driven by Coverity.
As soon as the remaining issues with the 3.1 branch are resolved, and
things cool down a bit, I plan on releasing 3.2.0 with all goodies included.
After that, I hope to find some time to work on:
- QRESYNC (rfc5162)
- ESEARCH (rfc4731)
- and maybe THREAD=references if I can think of a fast enough
implementation.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/[email protected]/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
