On 2016-07-05 14:21:46 +0200, Diego Biurrun wrote:
> ---
>  doc/APIchanges | 38 +++++++++++++++++++-------------------
>  1 file changed, 19 insertions(+), 19 deletions(-)
> 
> diff --git a/doc/APIchanges b/doc/APIchanges
> index d9e83bc..5df8a73 100644
> --- a/doc/APIchanges
> +++ b/doc/APIchanges
> @@ -13,72 +13,72 @@ libavutil:     2015-08-28
>  
>  API changes, most recent first:
>  
> -2016-xx-xx - xxxxxxx - lavu 55.19.0 - hwcontext_vaapi.h
> +2016-07-02 - 4926fa9 - lavu 55.19.0 - hwcontext_vaapi.h
>    Add driver quirks field to VAAPI-specific hwdevice and enum with
>    members AV_VAAPI_DRIVER_QUIRK_* to represent its values.
>  
> -2016-xx-xx - xxxxxxx - lavu 55.18.0 - pixdesc.h
> +2016-07-02 - b7c5f88 - lavu 55.18.0 - pixfmt.h
>    Add AV_PIX_FMT_P010(LE/BE).
>  
> -2016-xx-xx - xxxxxxx - lavc 57.24.0 - avcodec.h
> +2016-06-21 - 32c8359 - lavc 57.24.0 - avcodec.h
>    Decoders now export the frame timestamp as AVFrame.pts. It was
>    previously exported as AVFrame.pkt_pts, which is now deprecated.
>  
> -2016-xx-xx - xxxxxxx - lavu 55.16.0 - hwcontext.h hwcontext_qsv.h
> +2016-06-21 - 59e7361 - lavu 55.16.0 - hwcontext.h hwcontext_qsv.h
>    Add AV_HWDEVICE_TYPE_QSV and a new installed header with QSV-specific
>    hwcontext definitions.
>  
> -2016-xx-xx - xxxxxxx - lavc 57.23.0 - avcodec.h
> +2016-06-21 - e85f6f7 - lavc 57.23.0 - avcodec.h
>    AVCodecContext.hw_frames_ctx now may be used by decoders.
>  
> -2016-xx-xx - xxxxxxx - lavc 57.20.0 - avcodec.h
> +2016-06-12 - 90f469a - lavc 57.20.0 - avcodec.h
>    Add FF_PROFILE_H264_MULTIVIEW_HIGH and FF_PROFILE_H264_STEREO_HIGH.
>  
> -2016-xx-xx - xxxxxxx - lavu 55.13.0 - hwcontext.h
> +2016-05-26 - 1c9e861 - lavu 55.13.0 - hwcontext.h
>    Add av_hwdevice_ctx_create().
>  
> -2016-xx-xx - xxxxxxx - lavc 57.19.1 - avcodec.h
> +2016-05-24 - e47b8bb - lavc 57.19.1 - avcodec.h
>    Adjust values for JPEG 2000 profiles.

Listing the commit (ad61da05) which changed the values is more 
informative then the commit adjusting the version.

Otherwise ok

Janne

_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to