On Fri, Mar 04, 2016 at 01:34:55PM +, Derek Buitenhuis wrote:
> On 3/3/2016 7:50 PM, Michael Niedermayer wrote:
> > The io_open/close callbacks afterwards seem direct access IIUC
> > so its not possible to remove or add any fields prior
> >
> > though maybe they have been added so recently tha
On 3/4/2016 3:02 PM, James Almer wrote:
> ry to non break ABI just yet, leave it as last resort. We did it not even
> half a year ago, and we'd have to push every single scheduled deprecation.
> If this can be resolved moving only the new entries then that's preferable.
OK I did it this way.
- De
On 3/4/2016 10:34 AM, Derek Buitenhuis wrote:
> On 3/3/2016 7:50 PM, Michael Niedermayer wrote:
>> The io_open/close callbacks afterwards seem direct access IIUC
>> so its not possible to remove or add any fields prior
>>
>> though maybe they have been added so recently that its ok to move
>> them
On 3/3/2016 7:50 PM, Michael Niedermayer wrote:
> The io_open/close callbacks afterwards seem direct access IIUC
> so its not possible to remove or add any fields prior
>
> though maybe they have been added so recently that its ok to move
> them above all "no direct access" fields
> or maybe iam m
On Thu, Mar 03, 2016 at 05:18:03PM +, Derek Buitenhuis wrote:
> Signed-off-by: Derek Buitenhuis
> ---
> This matches API with Libav, in a forthcoming merge, using our
> exisiting infastructure code.
>
> CC'd Michael, since he wrote the whitelisting code.
>
> This has been tested with FATE.
>
Signed-off-by: Derek Buitenhuis
---
This matches API with Libav, in a forthcoming merge, using our
exisiting infastructure code.
CC'd Michael, since he wrote the whitelisting code.
This has been tested with FATE.
---
Changelog | 1 +
doc/APIchanges|
