aboutsummaryrefslogtreecommitdiffstats
path: root/tools/make_chlayout_test
diff options
context:
space:
mode:
authorJames Almer <jamrial@gmail.com>2017-06-24 01:52:09 -0300
committerJames Almer <jamrial@gmail.com>2017-06-24 01:52:09 -0300
commite5bce8b4ce7b1f3a83998febdfa86a3771df96ce (patch)
tree01cdd4325e02b34c4dc9b19d7ef5591524e134f1 /tools/make_chlayout_test
parent349446e36f17261c84bbad45ab81d35f4a833a2b (diff)
downloadffmpeg-e5bce8b4ce7b1f3a83998febdfa86a3771df96ce.tar.gz
fate: update checksums for fate-lavf-ffm and fate-lavf-mxf
<@jamrial> durandal_1707: 04aa09c4bc broke fate-lavf-ffm and fate-lavf-mxf <@durandal_1707> how so? <@jamrial> one byte changes <@durandal_1707> jamrial: just update checksums <@jamrial> durandal_1707: but why did they change at all? the commit you reverted didn't affect them <@jamrial> why does reverting it affect these tests? <@jamrial> i don't think updating the checksum without knowing what changed is a good idea <@durandal_1707> jamrial: the lavfi core is in weird state after removal of recursive code <@durandal_1707> jamrial: the change is that older ones would get progressive flag set and new one doesnt <@jamrial> alright
Diffstat (limited to 'tools/make_chlayout_test')
0 files changed, 0 insertions, 0 deletions