On 6/30/2016 5:39 PM, Michael Niedermayer wrote: > does the following sound ok to you ? > i kept this very terse as most changes in the file are tersly > documented only
Yeah, the proper place for an explanation as to why we're doing this is not APIChanges. > > commit 518b526aa310c963f42a76f48ce8fa1418dc0afe > Author: Michael Niedermayer <mich...@niedermayer.cc> > Date: Thu Jun 30 18:12:41 2016 +0200 > > doc/APIchanges: document the lavu/lavf field moves > > Based-on: patch by James Almer > Signed-off-by: Michael Niedermayer <mich...@niedermayer.cc> > > diff --git a/doc/APIchanges b/doc/APIchanges > index 47106c2..354b8b4 100644 > --- a/doc/APIchanges > +++ b/doc/APIchanges > @@ -15,6 +15,14 @@ libavutil: 2015-08-28 > > API changes, most recent first: > > +2016-06-30 - c1c7e0ab - lavf 57.41.100 - avformat.h > + Moved codecpar field from AVStream to the end of the struct, so that > + the following private fields are in the same location as in FFmpeg 3.0. > + > +2016-06-30 - 042fb69d - lavu 55.28.100 - frame.h > + Moved hw_frames_ctx field from AVFrame to the end of the struct, so that > + the following private fields are in the same location as in FFmpeg 3.0. Sounds good. Maybe also mention the lavf/lavu versions we're "matching" with this change (lavf 57.32.100 and lavu 55.17.100 i think) and not just the ffmpeg version. APIChanges is after all about the libraries. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
