A plan for new-master

[joachifm]

There are subtle issues with the 0.5 series of libmpd-haskell. More
specifically,

0ab7c457265ce544e914c7017f236624e6f996da
263236a395ecf6b1c975ec8d8c4c566ecc05326c
fa83e9599b77465740b69cf5056702e5d38d1a5d

introduce changes that are not ready for the mainline (I was way too
trigger happy when I included them in the first place).

I have created `new-master` which is based on 0.4.2, and is similar to
0.5 sans the above commits, as a short-term solution to this problem.

My plan is to first make sure there are no more implementation bugs in
`new-master`, and then incrementally backport changes from fa83e95
(such as the data structure improvements and API tweaks).

Then we can start looking at redoing the experimental changes and put
those
in a separate branch until the issues have been worked out.

[Joachim Fasting]

Ok, I've merged `new-master' with `master'. From now on, only
trivial changes or bugfixes go into `master' until there are
absolutely no more implementation bugs.