summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2015-12-31 16:23:44 +0100
committerwm4 <wm4@nowhere>2015-12-31 16:23:44 +0100
commit9b87d1999fd7a3588bbcedddeab47f0bef34ac88 (patch)
tree02121a42e8d0f5ce962c2639aae120644e0e1e8a
parentcfa1a61e39f218fe4dc288ddf44b85200ff35fdd (diff)
downloadlibass-9b87d1999fd7a3588bbcedddeab47f0bef34ac88.tar.bz2
libass-9b87d1999fd7a3588bbcedddeab47f0bef34ac88.tar.xz
Changelog: create entry for the next version
It's always such a bother to write the changelog on release. And in fact, there is no reason why the changelog should be written on release. It's easier to edit it as we commit fixes or features. I'm adding the changelog entries for the past two commits, and in the future, we should add entries as we commit bug fixes or new features.
-rw-r--r--Changelog6
1 files changed, 6 insertions, 0 deletions
diff --git a/Changelog b/Changelog
index cdef2ad..e7a25f4 100644
--- a/Changelog
+++ b/Changelog
@@ -1,3 +1,9 @@
+libass (0.13.2 - unreleased)
+ * Bug fixes
+ * Fix an issue with the new duplicate checking, which could lead to
+ missing subtitles after seeking.
+ * Fix a crash with CoreText under specific circumstances
+
libass (0.13.1)
* Much faster duplicate event check in ass_process_chunk. This can
bring a large speedup for embedded subtitles with lots of events.