[Ffmpeg-devel] [PATCH] mjpeg cleanup and again interlaced fix
Sun Apr 15 03:40:32 CEST 2007
On Sun, Apr 15, 2007 at 02:23:24AM +0200, Baptiste Coudurier wrote:
> > [...]
> >>>>>> You broke ./configure --enable-debug with your h264 bugs without asking
> >>>>>> anyone and without even willing to fix, and you just said "send patch",
> >>>>>> that proves how you care about others.
> >>>>> its a gcc bug ...
> >>>> You still broke something working, so you must reverse it. Your solution
> >>>> was not acceptable.
> >>> if a changes in the source cause some version of gcc to fail (or even all
> >>> versions of gcc)
> >>> due to a gcc bug, this still is a gcc bug and not one in ffmpeg, as its
> >>> not a ffmpeg bug theres no reason why it should be reversed
> >> I don't think that is a valid reason to break other working features.
> >> You MUST deal with gcc bugs like it or not, and not breaking working
> >> features OR you must implement YOURSELF the check for available
> >> registers, not saying that you don't care about PIC or that you are lazy.
> > who are you that you tell me what i "MUST"?
> Aren't you prefering democracy ?
> In a democracy I can say what Im thinking.
yes and you seem to do that, so i see no problem here
> And Im a developer following ffmpeg since more than 1 year now, and an
could very well be iam not disagreeing
but where is the point? democracy is "rule by the people" you dont
qualify as people, you are one out of many
> Anyway I noticed you did not even care to mention where a problem with a
> mov having a wrong height/width caused problem.
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
There will always be a question for which you do not know the correct awnser.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the ffmpeg-devel