On Thu, May 19, 2016 at 09:47:10AM +0200, Nicolas George wrote:
> It passes packets unchanged with a very low overhead.
> Using it allows to have the same code path when bitstream filtering
> is not used, making the code simpler and avoiding bitroting.
> The filter can not be disabled so that applications can rely on it.
> It is added out of alphabetical order to keep the regularity.
> 
> TODO: minor bump.
> Signed-off-by: Nicolas George <geo...@nsup.org>
> ---
>  libavcodec/bitstream_filters.c |  3 +++
>  libavcodec/bsf.c               | 16 ++++++++++++++++
>  2 files changed, 19 insertions(+)
> 
> 
> Updated to the new list format.
> 
> Name unchanged, already explained.

LGTM

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.

Attachment: signature.asc
Description: Digital signature

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to