On Thu, Jan 26, 2012 at 12:51:19PM +0100, Anton Khirnov wrote:
> ---
>  src/index |   24 ++++++++++++++++++++++++
>  1 files changed, 24 insertions(+), 0 deletions(-)
> 
> diff --git a/src/index b/src/index
> index a09615a..daa0d21 100644
> --- a/src/index
> +++ b/src/index
> @@ -33,6 +33,30 @@ with the latest developments by subscribing to both the
>  
>  <h1>News</h1>
>  
> +<a name="small_bump"></a><h3>Jan 26 2012</h3>

What's small about this big bump?

> +<p>
> +Major versions of the <b>libavformat</b> and <b>libavcodec</b> libraries have
> +been bumped, thus <b>breaking binary and API compatibility</b> with the 
> recent

I'd say s/binary/ABI/.

> +0.8 release. As usual, the ABI should be considered unstable until further
> +notice (a few weeks at most).

Shouldn't the API be considered unstable as well?

> +<p>
> +This step allows us to remove a large amount of obsolete code (over 3000 
> lines).
> +Users who still didn't update to the latest API must do so now to be able to 
> use

did not

Avoid contractions in written English.

> +<p>
> +Furthermore, the legacy <b>ffmpeg</b> conversion tool has been removed. Only
> +<b>avconv</b> is available now. Shared builds of Libav now also disable the
> +<b>avserver</b> tool. <b>avserver</b> can only be linked with Libav 
> statically
> +because it uses internal symbols (volunteers to fix this are very welcome).

internal library symbols

Diego
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to