From: Andreas Sturmlechner <asturm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Luca Barbato <lu_zero@gentoo.org>, media-video@gentoo.org
Subject: [gentoo-dev] Re: The state of libav stabilisation
Date: Sat, 15 Sep 2018 17:06:46 +0200 [thread overview]
Message-ID: <3780047.rO1b2bk0cO@tuxk10> (raw)
In-Reply-To: <7de7986c-e65d-3b87-9dac-15167ec739c7@gentoo.org>
On Donnerstag, 13. September 2018 12:44:24 CEST Luca Barbato wrote:
> I guess nobody had time to, libav-12 is working correctly on those arches.
>
> Thanks for reminding us.
Thanks for getting it going. Could someone please add themselves as a
dedicated maintainer to media-video/libav? amd64 has a question regarding
stabilisation[1] and it seems that assigning media-video does not suffice.
Relaying via gentoo-dev list does not scale.
[1] https://bugs.gentoo.org/617508
prev parent reply other threads:[~2018-09-15 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 10:38 [gentoo-dev] The state of libav stabilisation Andreas Sturmlechner
2018-09-13 10:44 ` [gentoo-dev] " Luca Barbato
2018-09-15 15:06 ` Andreas Sturmlechner [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3780047.rO1b2bk0cO@tuxk10 \
--to=asturm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=lu_zero@gentoo.org \
--cc=media-video@gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox