summaryrefslogtreecommitdiffstats
path: root/libass
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 /libass
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.
Diffstat (limited to 'libass')
0 files changed, 0 insertions, 0 deletions