On Sat, 16 Aug 2014 11:59:20 -0700
Russ Allbery wrote:
> The problem, however, is that taking security seriously, while possibly
> necessary, is not sufficient. I'm glad that FFmpeg takes security
> seriously, but what FFmpeg needs is to *have fewer security bugs*.
That is very valuable advice.
On Sat, 16 Aug 2014 23:29:56 +0800
Thomas Goirand wrote:
> On 08/15/2014 11:53 PM, The Wanderer wrote:
> > It's also something the Linux kernel is still doing, with apparent
> > success.
>
> Yes, the Linux kernel is a successful project. Does this mean using a
> list for reviewing patches is a g
On Tue, 12 Aug 2014 16:51:40 +0200
Matthias Urlichs wrote:
> Hi,
>
> wm4:
> > In fact, the API cleanup is an ongoing process, and is what causes the
> > incompatibilities with each release. For example, a C library should
> > have a consistent naming schema. FFmpeg/
On Tue, 12 Aug 2014 02:54:39 +0200
Matthias Urlichs wrote:
> Hi,
>
> wm4:
> > Build something on a newer glibc system, and try to run the binary on
> > an older system. It most likely won't work - even if it could in
> > theory. (At least it was this way s
On Mon, 11 Aug 2014 18:34:23 -0400
Theodore Ts'o wrote:
> On Mon, Aug 11, 2014 at 10:53:56PM +0200, wm4 wrote:
> >
> > To be fair, FFmpeg does its own "manual" symbol versioning by appending
> > increasing numbers to function names. But the real problem are
On Mon, 11 Aug 2014 20:40:28 +0200
Reimar Döffinger wrote:
> Hello,
>
> Apologies for not being able to resist answering even if it is getting
> off-topic.
>
> On Sun, Aug 10, 2014 at 05:43:33PM -0400, Theodore Ts'o wrote:
> > On Sun, Aug 10, 2014 at 12:25:33AM -0700, Andrew Kelley wrote:
> > >
6 matches
Mail list logo