[FFmpeg-devel] [PATCH] Remove the ffserver program and the ffm muxer/demuxer
jamrial at gmail.com
Mon Nov 28 17:52:41 EET 2016
On 11/28/2016 12:24 PM, Nicolas George wrote:
> L'octidi 8 frimaire, an CCXXV, James Almer a écrit :
>> Threats? The only thing i see are reminders of what should have happened
>> earlier and will happen soon, as discussed an announced.
> Reminding of unpleasant things over which you have total control, that
> is called threats.
> "You will burn yourself." -> this is a warning.
> "I will burn you." -> that is a threat.
> Since ffserver will not remove itself, it is indeed a threat.
No Nicolas. It's a reminder that this patch, as discussed and announced, will
>> No, i want a project decision to finally go through. I don't give a shit
>> about the program. If you see me "emotional" is because i can't believe my
>> eyes when i see all this shit happening only after the decision was made
>> and not when actual development work was requested, or when the *final*
>> discussion was taking place.
>> You all should have shown then. You didn't.
> You act quite emotional over something you "don't give a shit" about.
I don't care about ffserver. I do care about the consequences of a bunch of
people that showed up very late to the party getting away with trying to
override an old project decision right when it was going to be made effective.
I'm here to make sure that doesn't happen.
>> Every patch and change that's being done now are direct consequence and
>> effect of the decision to drop ffserver. It has remained broken,
>> unmaintained and bitrotting for years but now that we have reached the
>> fateful day, ffserver is suddenly more important than the h264 decoder.
> This is a "post hoc ergo propter hoc" fallacy.
> The recent patches and the proposal to remove ffserver are not a
> consequence of each other but both consequence of this single fact: the
> internal APIs that ffserver is (ab)using are being changed and it is
> blocking the merges.
This is a lie and you know it, regardless of how fancy you try to make it
ffserver started getting all these little changes right after the removal
was going to be set in motion for the 3.2 release. Reynaldo even sent an
email stating as much. That these are meant to be efforts to make it not
depend on public api so it can live out of tree for whoever cares about it.
A little while after that, Andreas and such started to use said efforts as
an argument to "prove" ffserver was still being maintained.
Look it up, stop trying to rewrite history and stop being part of the
aforementioned malicious behavior.
> The patches unblock the merges, therefore the removal is no longer
Too bad the decision was made and announced. Had this happened months or
years ago, when help was requested and promptly ignored, it wouldn't have
ended up like this.
>> This patch *should* have been committed weeks ago
> I will remind you that most contributors work on the project on their
> free time. If you care so much about ffserver's code (apparently you do,
> or you would not be arguing so much about it), you could have sponsored
> them to work on it earlier.
If you want to lose time trying to change a decision made by a group of
people, go to England and save them from Brexit. You'll probably have as
much success trying to change that as you'll have it here.
More information about the ffmpeg-devel