[FFmpeg-devel] [PATCH v2 0/8] Merge lazy filter initialization in ffmpeg CLI

[Carl Eugen Hoyos]

2017-02-15 17:47 GMT+01:00 wm4 <nfxjfg at googlemail.com>:

> What I don't want is that you post a new failing case approximately
> every 24 hours, with no end in sight, and with the implication that
> it's supposed to be fixed before merge. At this rate it could take
> weeks, with every day following the same pattern.

Aren't you simply describing a general development and review
process here?

> Maybe you could at least maybe analyze breakages yourself before
> pointing them out. That would be helpful.

(Given that Michael had already answered this, mentioning it
again seems quite offensive to me.)

> Besides even regular patches can have regressions. For example, with
> the edit list patches, entire files didn't decode. (Now I don't want to
> single out those patches specifically - they're simply in my recent
> memory.)

Not sure what you are implying here or how the commits are related
but these patches were among the most important changes in FFmpeg
in a long time and they were on the mailing list for some time waiting
for reviews.

That's apart from the fact that the author is happy to look into issues
as soon as he knows about them (he said so and has shown this).

>> In projects based on fork & merge the people doing the merge would not
>> fix regressions, the authors or person making a pull request would fix
>> the regressions either before merge or after through a subsequent pull
>> request or patch.
>
> I have no idea what you're talking about.
>
> This is not a typical merge.

> We're dependent on merging Libav

What does that mean?

> from a "non cooperating" foreign project. It wasn't my idea either. We're
> behind by over 500 commits, and there are Libav features which people
> need/want to have in FFmpeg.
>
>> In projects based on send patch and apply, the authors or patch
>> submitter fixes regressions and resubmit patches or submit new patches
>> if an issue is found after push.
>
> See above. If you want to stop merges, please say so.

> If not, you should probably try not to prevent them.

Just to clarify:
Michael has repeatedly written that he wants the merges to happen.

Carl Eugen