From: Arne Babenhauserheide <arne_bab@web.de>
To: Leo Famulari <leo@famulari.name>
Cc: 41468-done@debbugs.gnu.org
Subject: bug#41468: update libaom to 2.0.0
Date: Sat, 23 May 2020 10:55:02 +0200 [thread overview]
Message-ID: <87r1vbqbdl.fsf@web.de> (raw)
In-Reply-To: <20200522233636.GA14281@jasmine.lan>
Leo Famulari <leo@famulari.name> writes:
> On Sat, May 23, 2020 at 12:49:20AM +0200, Arne Babenhauserheide wrote:
>> this updates libaom to 2.0.0
>
> Nice! It should be a lot faster than before :)
>
>> Tested: ffmpeg still works.
>
> Thanks for saying how you tested it. Pushed as
> 6597893ba27153efd61bc28b15c1f4cd1aab2864 along with updates to dav1d and
> libavif.
Cool! Thank you!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
prev parent reply other threads:[~2020-05-23 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 22:49 bug#41468: update libaom to 2.0.0 Arne Babenhauserheide
2020-05-22 23:36 ` Leo Famulari
2020-05-23 8:55 ` Arne Babenhauserheide [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1vbqbdl.fsf@web.de \
--to=arne_bab@web.de \
--cc=41468-done@debbugs.gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).