:)
Thank you both for your time!
George
On Wed, Aug 31, 2016 at 2:37 AM, Michael Niedermayer wrote:
> On Wed, Aug 31, 2016 at 04:24:36AM -0400, Ronald S. Bultje wrote:
> > Hi George,
> >
> > On Tue, Aug 30, 2016 at 8:47 PM, George Burgess
> wrote:
> >
> > > Tha
ks,
George
On Tue, Aug 30, 2016 at 4:10 PM, Ronald S. Bultje
wrote:
> Hi,
>
> On Tue, Aug 30, 2016 at 6:49 PM, George Burgess IV
> wrote:
>
>> ChromeOS is adopting a new FORTIFY implementation tailored for clang. As
>> an artifact of how this new FORTIFY is implemented,
: George Burgess IV
---
If anyone feels that more comments would be useful, I'll add them above some of
the char* casts, so it's a bit more obvious why we have said casts.
Testing methodology was "run `make fate` and see what doesn't build." If there
are other targets that
n Tue, Aug 30, 2016 at 3:05 AM, Michael Niedermayer wrote:
> On Tue, Aug 30, 2016 at 12:11:42AM -0700, George Burgess IV wrote:
> > ChromeOS is adopting a new FORTIFY implementation tailored for clang. As
> > an artifact of how this new FORTIFY is implemented, a handful of
>
: George Burgess IV
---
libavutil/opt.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/libavutil/opt.c b/libavutil/opt.c
index cd16bd1..f7f5225 100644
--- a/libavutil/opt.c
+++ b/libavutil/opt.c
@@ -733,7 +733,8 @@ int av_opt_get(void *obj, const char *name, int
