On Tue, Dec 27, 2016 at 7:31 PM, Anton Khirnov wrote:
> Extend the width/height doy to clarify that it should store coded
> values.
s/doy/documentation/ ?
> ---
> doc/APIchanges | 4
> libavutil/frame.c | 4
> libavutil/frame.h | 28
We could decide to go over all the API and use the correct types all over.
lu
___
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
On Fri, 30 Dec 2016 10:58:04 +0100
"Diego Biurrun" wrote:
> On Fri, Dec 30, 2016 at 10:32:46AM +0100, wm4 wrote:
> > On Wed, 28 Dec 2016 17:34:33 +0100
> > "Diego Biurrun" wrote:
> > > On Wed, Dec 28, 2016 at 07:47:58AM +0100, Luca Barbato wrote:
> > > >
On Fri, Dec 30, 2016 at 10:32:46AM +0100, wm4 wrote:
> On Wed, 28 Dec 2016 17:34:33 +0100
> "Diego Biurrun" wrote:
> > On Wed, Dec 28, 2016 at 07:47:58AM +0100, Luca Barbato wrote:
> > > On 27/12/2016 19:31, Anton Khirnov wrote:
> > > > Extend the width/height doy to clarify
On Wed, 28 Dec 2016 17:34:33 +0100
"Diego Biurrun" wrote:
> On Wed, Dec 28, 2016 at 07:47:58AM +0100, Luca Barbato wrote:
> > On 27/12/2016 19:31, Anton Khirnov wrote:
> > > Extend the width/height doy to clarify that it should store coded
> > > values.
> > > ---
> > >
On Wed, Dec 28, 2016 at 07:47:58AM +0100, Luca Barbato wrote:
> On 27/12/2016 19:31, Anton Khirnov wrote:
> > Extend the width/height doy to clarify that it should store coded
> > values.
> > ---
> > doc/APIchanges | 4
> > libavutil/frame.c | 4
> > libavutil/frame.h | 28
On 27/12/2016 19:31, Anton Khirnov wrote:
> Extend the width/height doy to clarify that it should store coded
> values.
> ---
> doc/APIchanges | 4
> libavutil/frame.c | 4
> libavutil/frame.h | 28 +++-
> libavutil/version.h | 2 +-
> 4 files
Extend the width/height doy to clarify that it should store coded
values.
---
doc/APIchanges | 4
libavutil/frame.c | 4
libavutil/frame.h | 28 +++-
libavutil/version.h | 2 +-
4 files changed, 36 insertions(+), 2 deletions(-)
diff --git