On Fri, Apr 20, 2018 at 02:31:59AM +0200, Michael Niedermayer wrote:
> On Thu, Apr 19, 2018 at 01:31:33PM +0200, Hendrik Leppkes wrote:
> > On Wed, Apr 18, 2018 at 11:15 PM, Michael Niedermayer
> > wrote:
> > > On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes
On Thu, Apr 19, 2018 at 01:31:33PM +0200, Hendrik Leppkes wrote:
> On Wed, Apr 18, 2018 at 11:15 PM, Michael Niedermayer
> wrote:
> > On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote:
> >> On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer
> >>
On Thu, 19 Apr 2018 17:01:56 +0200
Nicolas George wrote:
> James Almer (2018-04-19):
> > It would have not been backwards compatible in such scenario to load at
> > runtime an hypotetical 3.4.x lavf library with that change in an
> > application that was built against 3.3.x or
James Almer (2018-04-19):
> It would have not been backwards compatible in such scenario to load at
> runtime an hypotetical 3.4.x lavf library with that change in an
> application that was built against 3.3.x or older. Regardless of 0 being
> defined as EOF or not in documentation, the behavior
On Thu, 19 Apr 2018 11:47:54 -0300
James Almer wrote:
> On 4/19/2018 11:43 AM, wm4 wrote:
> > On Thu, 19 Apr 2018 16:33:47 +0200
> > Nicolas George wrote:
> >
> >> James Almer (2018-04-19):
> >>> Had it been in 3.4 it would have mean a considerable ABI
On 4/19/2018 11:43 AM, wm4 wrote:
> On Thu, 19 Apr 2018 16:33:47 +0200
> Nicolas George wrote:
>
>> James Almer (2018-04-19):
>>> Had it been in 3.4 it would have mean a considerable ABI breakage as
>>> well, at least without the eventual backwards compat change.
>>
>> Can you
On 4/19/2018 11:33 AM, Nicolas George wrote:
> James Almer (2018-04-19):
>> Had it been in 3.4 it would have mean a considerable ABI breakage as
>> well, at least without the eventual backwards compat change.
>
> Can you explain why you think that?
>
> When advising on these changes and
On Thu, 19 Apr 2018 16:33:47 +0200
Nicolas George wrote:
> James Almer (2018-04-19):
> > Had it been in 3.4 it would have mean a considerable ABI breakage as
> > well, at least without the eventual backwards compat change.
>
> Can you explain why you think that?
>
> When
James Almer (2018-04-19):
> Had it been in 3.4 it would have mean a considerable ABI breakage as
> well, at least without the eventual backwards compat change.
Can you explain why you think that?
When advising on these changes and reviewing patches, I was very careful
that they do not introduce
On 4/19/2018 3:49 AM, Hendrik Leppkes wrote:
> On Thu, Apr 19, 2018 at 12:56 AM, wm4 wrote:
>> On Thu, 19 Apr 2018 00:40:21 +0200
>> Michael Niedermayer wrote:
>>
>>> On Wed, Apr 18, 2018 at 11:55:09PM +0200, Paul B Mahol wrote:
On 4/18/18, wm4
On Thu, 19 Apr 2018 08:49:07 +0200
Hendrik Leppkes wrote:
> On Thu, Apr 19, 2018 at 12:56 AM, wm4 wrote:
> > On Thu, 19 Apr 2018 00:40:21 +0200
> > Michael Niedermayer wrote:
> >
> >> On Wed, Apr 18, 2018 at 11:55:09PM
On Wed, Apr 18, 2018 at 11:15 PM, Michael Niedermayer
wrote:
> On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote:
>> On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer
>> wrote:
>> > On Sat, Apr 14, 2018 at 02:04:43PM +0200, Michael
On Thu, 19 Apr 2018 12:49:21 +0200
Nicolas George wrote:
> Hendrik Leppkes (2018-04-19):
> > Lets just fix the issues and move on, there is no point in more arguing.
>
> Thanks (and also thanks to Michael).
>
> When something has been badly designed for a long time (and this
Hendrik Leppkes (2018-04-19):
> Lets just fix the issues and move on, there is no point in more arguing.
Thanks (and also thanks to Michael).
When something has been badly designed for a long time (and this
particular issue predates FFmpeg: the Unix socket API itself is bad,
FFmpeg only followed
On Thu, 19 Apr 2018 08:49:07 +0200
Hendrik Leppkes wrote:
> On Thu, Apr 19, 2018 at 12:56 AM, wm4 wrote:
> > On Thu, 19 Apr 2018 00:40:21 +0200
> > Michael Niedermayer wrote:
> >
> >> On Wed, Apr 18, 2018 at 11:55:09PM
On Thu, 19 Apr 2018 02:19:06 +0200
Michael Niedermayer wrote:
> On Thu, Apr 19, 2018 at 12:56:05AM +0200, wm4 wrote:
> > On Thu, 19 Apr 2018 00:40:21 +0200
> > Michael Niedermayer wrote:
> >
> > > On Wed, Apr 18, 2018 at 11:55:09PM +0200, Paul
On Thu, Apr 19, 2018 at 12:56 AM, wm4 wrote:
> On Thu, 19 Apr 2018 00:40:21 +0200
> Michael Niedermayer wrote:
>
>> On Wed, Apr 18, 2018 at 11:55:09PM +0200, Paul B Mahol wrote:
>> > On 4/18/18, wm4 wrote:
>> > > On Wed, 18
On Thu, Apr 19, 2018 at 12:56:05AM +0200, wm4 wrote:
> On Thu, 19 Apr 2018 00:40:21 +0200
> Michael Niedermayer wrote:
>
> > On Wed, Apr 18, 2018 at 11:55:09PM +0200, Paul B Mahol wrote:
> > > On 4/18/18, wm4 wrote:
> > > > On Wed, 18 Apr 2018
On Thu, 19 Apr 2018 00:40:21 +0200
Michael Niedermayer wrote:
> On Wed, Apr 18, 2018 at 11:55:09PM +0200, Paul B Mahol wrote:
> > On 4/18/18, wm4 wrote:
> > > On Wed, 18 Apr 2018 23:15:47 +0200
> > > Michael Niedermayer
On Wed, Apr 18, 2018 at 11:55:09PM +0200, Paul B Mahol wrote:
> On 4/18/18, wm4 wrote:
> > On Wed, 18 Apr 2018 23:15:47 +0200
> > Michael Niedermayer wrote:
> >
> >> On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote:
> >> > On Mon, Apr
On 4/18/18, wm4 wrote:
> On Wed, 18 Apr 2018 23:15:47 +0200
> Michael Niedermayer wrote:
>
>> On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote:
>> > On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer
>> >
On Wed, 18 Apr 2018 23:15:47 +0200
Michael Niedermayer wrote:
> On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote:
> > On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer
> > wrote:
> > > On Sat, Apr 14, 2018 at 02:04:43PM +0200,
On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote:
> On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer
> wrote:
> > On Sat, Apr 14, 2018 at 02:04:43PM +0200, Michael Niedermayer wrote:
> >> On Fri, Apr 13, 2018 at 12:53:08AM +0200, Michael Niedermayer
On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer
wrote:
> On Sat, Apr 14, 2018 at 02:04:43PM +0200, Michael Niedermayer wrote:
>> On Fri, Apr 13, 2018 at 12:53:08AM +0200, Michael Niedermayer wrote:
>> > On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer
On Mon, Apr 16, 2018 at 03:14:55PM +0100, Rostislav Pehlivanov wrote:
> On 16 April 2018 at 12:40, Timo Teras wrote:
>
> > On Mon, 16 Apr 2018 13:24:48 +0200
> > Michael Niedermayer wrote:
> >
> > > release/4.0 branched
> > > next is the release in a
On 16 April 2018 at 12:40, Timo Teras wrote:
> On Mon, 16 Apr 2018 13:24:48 +0200
> Michael Niedermayer wrote:
>
> > release/4.0 branched
> > next is the release in a few days.
> > If theres something i should wait for please say so and CC me
> > also
On Mon, 16 Apr 2018 13:24:48 +0200
Michael Niedermayer wrote:
> release/4.0 branched
> next is the release in a few days.
> If theres something i should wait for please say so and CC me
> also please backport all bugfixes to 4.0
I was hoping to get my patches in for the
On Sat, Apr 14, 2018 at 02:04:43PM +0200, Michael Niedermayer wrote:
> On Fri, Apr 13, 2018 at 12:53:08AM +0200, Michael Niedermayer wrote:
> > On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer wrote:
> > > Hi
> > >
> > > Its 4 months since 3.4 was branched so its time for a new major
On Fri, Apr 13, 2018 at 12:53:08AM +0200, Michael Niedermayer wrote:
> On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer wrote:
> > Hi
> >
> > Its 4 months since 3.4 was branched so its time for a new major release
> >
> > Is 4.0 or 3.5 preferred ?
> > Any name suggestions ?
> >
> >
On 4/13/2018 10:48 AM, Michael Niedermayer wrote:
> On Fri, Apr 13, 2018 at 10:33:32AM -0300, James Almer wrote:
>> On 4/13/2018 9:59 AM, Michael Niedermayer wrote:
>>> On Thu, Apr 12, 2018 at 10:17:51PM -0300, James Almer wrote:
On 4/12/2018 9:11 PM, Michael Niedermayer wrote:
>>> [...]
>>>
On Fri, Apr 13, 2018 at 10:33:32AM -0300, James Almer wrote:
> On 4/13/2018 9:59 AM, Michael Niedermayer wrote:
> > On Thu, Apr 12, 2018 at 10:17:51PM -0300, James Almer wrote:
> >> On 4/12/2018 9:11 PM, Michael Niedermayer wrote:
> > [...]
> >
> >>>
> >>>
> and apply the fix to the c11
On 4/13/2018 9:59 AM, Michael Niedermayer wrote:
> On Thu, Apr 12, 2018 at 10:17:51PM -0300, James Almer wrote:
>> On 4/12/2018 9:11 PM, Michael Niedermayer wrote:
> [...]
>
>>>
>>>
and apply the fix to the c11 check in configure.
>>>
>>> you want me to apply it ?
>>> or i misunderstand ?
>>
On Thu, Apr 12, 2018 at 10:17:51PM -0300, James Almer wrote:
> On 4/12/2018 9:11 PM, Michael Niedermayer wrote:
[...]
> >
> >
> >> and apply the fix to the c11 check in configure.
> >
> > you want me to apply it ?
> > or i misunderstand ?
>
> You confirmed it worked ("foo += bar" and "bar =
On Thu, Apr 12, 2018 at 10:17:51PM -0300, James Almer wrote:
> On 4/12/2018 9:11 PM, Michael Niedermayer wrote:
> > On Thu, Apr 12, 2018 at 07:59:25PM -0300, James Almer wrote:
> >> On 4/12/2018 7:53 PM, Michael Niedermayer wrote:
> >>> On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer
On Fri, Apr 13, 2018 at 12:59 AM, James Almer wrote:
> a bunch of msvc miscompilation failures that Microsoft will not fix.
A bunch of those are apparently fixed in an upcoming compiler update,
Martin reported those (for VS2017)
What remains we'll have to see afterwards, its
On 4/12/2018 10:17 PM, James Almer wrote:
> On 4/12/2018 9:11 PM, Michael Niedermayer wrote:
>> On Thu, Apr 12, 2018 at 07:59:25PM -0300, James Almer wrote:
>>> On 4/12/2018 7:53 PM, Michael Niedermayer wrote:
On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer wrote:
> Hi
>
On 4/12/2018 9:11 PM, Michael Niedermayer wrote:
> On Thu, Apr 12, 2018 at 07:59:25PM -0300, James Almer wrote:
>> On 4/12/2018 7:53 PM, Michael Niedermayer wrote:
>>> On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer wrote:
Hi
Its 4 months since 3.4 was branched so its
On Thu, Apr 12, 2018 at 07:59:25PM -0300, James Almer wrote:
> On 4/12/2018 7:53 PM, Michael Niedermayer wrote:
> > On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer wrote:
> >> Hi
> >>
> >> Its 4 months since 3.4 was branched so its time for a new major release
> >>
> >> Is 4.0 or 3.5
On 4/12/2018 7:53 PM, Michael Niedermayer wrote:
> On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer wrote:
>> Hi
>>
>> Its 4 months since 3.4 was branched so its time for a new major release
>>
>> Is 4.0 or 3.5 preferred ?
>> Any name suggestions ?
>>
>> If there are no objections i
On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer wrote:
> Hi
>
> Its 4 months since 3.4 was branched so its time for a new major release
>
> Is 4.0 or 3.5 preferred ?
> Any name suggestions ?
>
> If there are no objections i will likely make that release in the next weeks
more
Hi,
On 19.02.2018 02:50, Michael Niedermayer wrote:
> Hi
>
> Its 4 months since 3.4 was branched so its time for a new major release
>
> Is 4.0 or 3.5 preferred ?
> Any name suggestions ?
>
> If there are no objections i will likely make that release in the next weeks
I would like to see the
Reto Kromer wrote:
>I suggest as well to move the 2.8 branch from the Releases to
>the Old Releases.
I just noticed that the day before yesterday 2.8.14 has been
released, therefore please ignore my suggestion. Thank you!
___
ffmpeg-devel mailing list
On Mon, 19 Feb 2018, Michael Niedermayer wrote:
Hi
Its 4 months since 3.4 was branched so its time for a new major release
Is 4.0 or 3.5 preferred ?
4.0
Any name suggestions ?
If there are no objections i will likely make that release in the next weeks
Removal of the nvenc headers was
Michael Niedermayer wrote:
>Is 4.0 or 3.5 preferred ?
I would prefer 4.0 for the reasons already mentioned by others.
I suggest as well to move the 2.8 branch from the Releases to
the Old Releases.
>Any name suggestions ?
>I do not agree with what you have to say, but I'll defend to
>the
On 2/19/2018 1:31 PM, Kieran Kunhya wrote:
> On Mon, 19 Feb 2018 at 16:06 James Almer wrote:
>
>> On 2/19/2018 5:54 AM, Paul B Mahol wrote:
>>> On 2/19/18, James Almer wrote:
On 2/18/2018 10:50 PM, Michael Niedermayer wrote:
> Hi
>
> Its 4
On Mon, 19 Feb 2018 at 16:06 James Almer wrote:
> On 2/19/2018 5:54 AM, Paul B Mahol wrote:
> > On 2/19/18, James Almer wrote:
> >> On 2/18/2018 10:50 PM, Michael Niedermayer wrote:
> >>> Hi
> >>>
> >>> Its 4 months since 3.4 was branched so its time for a
On 2/19/2018 5:54 AM, Paul B Mahol wrote:
> On 2/19/18, James Almer wrote:
>> On 2/18/2018 10:50 PM, Michael Niedermayer wrote:
>>> Hi
>>>
>>> Its 4 months since 3.4 was branched so its time for a new major release
>>>
>>> Is 4.0 or 3.5 preferred ?
>>
>> Definitely 4.0. With
On 2/19/18, wm4 wrote:
> On Mon, 19 Feb 2018 09:54:57 +0100
> Paul B Mahol wrote:
>
>> On 2/19/18, James Almer wrote:
>> > On 2/18/2018 10:50 PM, Michael Niedermayer wrote:
>> >> Hi
>> >>
>> >> Its 4 months since 3.4 was branched so
On Mon, 19 Feb 2018 09:54:57 +0100
Paul B Mahol wrote:
> On 2/19/18, James Almer wrote:
> > On 2/18/2018 10:50 PM, Michael Niedermayer wrote:
> >> Hi
> >>
> >> Its 4 months since 3.4 was branched so its time for a new major release
> >>
> >> Is 4.0 or 3.5
On 2/19/18, James Almer wrote:
> On 2/18/2018 10:50 PM, Michael Niedermayer wrote:
>> Hi
>>
>> Its 4 months since 3.4 was branched so its time for a new major release
>>
>> Is 4.0 or 3.5 preferred ?
>
> Definitely 4.0. With the major bump, the removal of ffprobe and WinXP
On 2/18/2018 10:50 PM, Michael Niedermayer wrote:
> Hi
>
> Its 4 months since 3.4 was branched so its time for a new major release
>
> Is 4.0 or 3.5 preferred ?
Definitely 4.0. With the major bump, the removal of ffprobe and WinXP
support, catching up with the merge queue, plus a bunch of new
51 matches
Mail list logo