GitLab

Signed-off-by: Martin Storsjö <martin@martin.st>

It is not used in any filters currently and is inherently evil. If
passing binary data to filters is required in the future, it should be
done with some AVOptions-based system.

It will allow adding new fields to it without ABI breaks.

They are only useful inside filters and we don't allow user filters for
now.

It is only useful inside filters and we don't allow user filters for
now.

Those functions are only useful inside filters. It is better to not
support user filters until the API is more stable.

Signed-off-by: Mans Rullgard <mans@mansr.com>

It is pretty hopeless that other considerable projects will adopt
libavutil alone in other projects. Projects that need small footprint
are better off with more specialized libraries such as gnulib or rather
just copy the necessary parts that they need. With this in mind, nobody
is helped by having libavutil and libavcore split. In order to ease
maintenance inside and around FFmpeg and to reduce confusion where to
put common code, avcore's functionality is merged (back) to avutil.
Signed-off-by: Reinhard Tartler <siretart@tauware.de>

headers.

Originally committed as revision 25838 to svn://svn.ffmpeg.org/ffmpeg/trunk

timebase in the filter link.

Originally committed as revision 25649 to svn://svn.ffmpeg.org/ffmpeg/trunk

to the timestamp.

Originally committed as revision 25647 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 25447 to svn://svn.ffmpeg.org/ffmpeg/trunk