From 9b6c17db96879839d9ebae7b419007a2dcf304a1 Mon Sep 17 00:00:00 2001 From: Stein Magnus Jodal Date: Mon, 17 Sep 2012 00:03:48 +0200 Subject: [PATCH] docs: Cleanup changelog --- docs/changes.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/changes.rst b/docs/changes.rst index 27b8731b..1c516a0d 100644 --- a/docs/changes.rst +++ b/docs/changes.rst @@ -78,23 +78,23 @@ v0.8 (in development) - :issue:`72`: Created a Spotify track proxy that will switch to using loaded data as soon as it becomes available. -- :issue:`162`: Fixed bug when the MPD command ``playlistinfo`` is used with a - track position. Track position and CPID was intermixed, so it would cause a - crash if a CPID matching the track position didn't exist. - - :issue:`150`: Fix bug which caused some clients to block Mopidy completely. The bug was caused by some clients sending ``close`` and then shutting down the connection right away. This trigged a situation in which the connection cleanup code would wait for an response that would never come inside the event loop, blocking everything else. +- :issue:`162`: Fixed bug when the MPD command ``playlistinfo`` is used with a + track position. Track position and CPID was intermixed, so it would cause a + crash if a CPID matching the track position didn't exist. + - Fixed crash on lookup of unknown path when using local backend. -- :issue:`189` ``LOCAL_MUSIC_PATH`` and path handling in rest of settings has +- :issue:`189`: ``LOCAL_MUSIC_PATH`` and path handling in rest of settings has been updated so all of the code now uses the correct value. -- Fixed incorrect track URIs generated by ``parse_m3u`` code, generated tracks - are now relative to ``LOCAL_MUSIC_PATH``. +- Fixed incorrect track URIs generated by M3U playlist parsing code. Generated + tracks are now relative to ``LOCAL_MUSIC_PATH``. v0.7.3 (2012-08-11)