Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
Michael Niedermayer niedermayer.cc> writes: > can you list which regressions you spoke about https://trac.ffmpeg.org/query?keywords=~codecpar I was hoping that somebody understands and explains #5348 before closing it. Carl Eugen ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, May 18, 2016 at 07:55:59PM +0200, Michael Niedermayer wrote: > On Wed, May 18, 2016 at 01:32:13PM +, Carl Eugen Hoyos wrote: > > Derek Buitenhuis gmail.com> writes: > > > > > I would agree, but for some reason Carl feels he is exempt > > > from the FFmpeg developer rules. > > > > I should probably add that this is an interesting comment > > coming from somebody who breaks FFmpeg with nearly every > > commit and not only absolutely refuses to work on fixes but > > even blocks fixes if others want to help him. > > if you wish to call peoples attention to a regression bug so > more people and the author and commiter are aware of it. I think > its best to reply to the commit on ffmpeg-cvslog with a CC to > ffmpeg-devel and a link to the bugreport which contains instructions > how to reproduce. > That way anyone who has time sees it and can help fixing it ping can you list which regressions you spoke about i like to fix them before the release if thats possible [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The educated differ from the uneducated as much as the living from the dead. -- Aristotle signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, May 18, 2016 at 02:46:34PM +0100, Derek Buitenhuis wrote: > On 5/18/2016 2:32 PM, Carl Eugen Hoyos wrote: > > I should probably add that this is an interesting comment > > coming from somebody who breaks FFmpeg with nearly every > > commit and not only absolutely refuses to work on fixes but > > even blocks fixes if others want to help him. > > Frankly, this is nothing nothing but an ad hominem attack. > > I am tired of it. This happens constantly, and the community > is always silent[1], and far too accepting of such toxic behavior. > > It has given me far too much unneeded stress and sourness. The > complete inability of the community to address such behavior and > individuals is appalling. > > I've had enough. I've already distanced myself from the Libav > community recently for similar behavior, and I will be doing > so for the FFmpeg community as well now. > > Both are toxic communities. As of this email, I am unsubscribing > from both ffmpeg-devel and libav-devel. > > I hope both communities enjoy their little out of touch bubbles. > It seems I'm late to the party again... As some people like to remind me, I'm indeed guilty and staying silent when I should raise arms against the devil. But just like you, I assume many people here are also very tired of the fighting (be it "between" or "within" projects) and as a result don't feel like getting more involved in this. So, just like others in this thread, yes of course you have my support against sanctions wrt the non respect of the common technical workflow, and indeed more into to the other issue, the heated crap following. One thing I don't understand though, this kind of situation happens from time to time, and every single time there is like a hand of developers spouting hatred at a single or two individuals, and complaining along the lines "the project doesn't do shit about $issue", followed by a tendency to shift the blame onto the other people who might not give much of a thought about that particular issue, or simply don't necessarily want to be involved in. So instead of these explosive and abrasive behaviours (which I'm not even condemning), I'd suggest the people who are really unhappy about it to bring potential ways out of it. Why was it needed for Michael to step in with a code of conduct even though we know he is much more efficient at non political or writing stuff, and has/had a delicate position in the matter? Paul suggested an IRC meeting, which is probably a step in the good direction, but I think Kieran, wm4, or you Derek (maybe missing others), should have been the first to send a draft for a code of conduct + sanctions things, or whatever other plan you had in mind. You think someone else is going to take responsibility for this? Don't fool yourself, it's unlikely to happen. I understand the anger, I really do. But shouting about a 3rd fork, getting angry at Carl or leaving slamming the door does not look like it's going to help (this last sentence is not directly aimed at you, but more at the group looking for changes). It's sad to see all this anger energy not be transformed in something more constructive, and it will be another loss to see you leave. -- Clément B. signature.asc Description: PGP signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, May 18, 2016 at 01:32:13PM +, Carl Eugen Hoyos wrote: > Derek Buitenhuis gmail.com> writes: > > > I would agree, but for some reason Carl feels he is exempt > > from the FFmpeg developer rules. > > I should probably add that this is an interesting comment > coming from somebody who breaks FFmpeg with nearly every > commit and not only absolutely refuses to work on fixes but > even blocks fixes if others want to help him. if you wish to call peoples attention to a regression bug so more people and the author and commiter are aware of it. I think its best to reply to the commit on ffmpeg-cvslog with a CC to ffmpeg-devel and a link to the bugreport which contains instructions how to reproduce. That way anyone who has time sees it and can help fixing it I certainly have myself caused bugs and missed bugreports about them in the past [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Those who are best at talking, realize last or never when they are wrong. signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, May 18, 2016 at 12:30:25PM -0300, James Almer wrote: > On 5/18/2016 10:29 AM, Carl Eugen Hoyos wrote: > > Paul B Mahol gmail.com> writes: > > > >> Please attach actual patch with commit log message. > > > > As soon as you give a helpful comment for the Babyphone patch;-) > > He asked you to follow the FFmpeg patch submit rules, which requires the > usage of git format-patch with no exceptions. You replied with a passive > aggressive unrelated comment, and an ad hominem attack in another email. > > You're one of most unprofessional, disrespectful and condescending person please everyone try to stay polite and productive. Thanks [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Everything should be made as simple as possible, but not simpler. -- Albert Einstein signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On 5/18/2016 10:29 AM, Carl Eugen Hoyos wrote: > Paul B Mahol gmail.com> writes: > >> Please attach actual patch with commit log message. > > As soon as you give a helpful comment for the Babyphone patch;-) He asked you to follow the FFmpeg patch submit rules, which requires the usage of git format-patch with no exceptions. You replied with a passive aggressive unrelated comment, and an ad hominem attack in another email. You're one of most unprofessional, disrespectful and condescending person this project has ever seen. Don't expect anyone to side with you once a vote to kick you out is started. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
Le decadi 30 floréal, an CCXXIV, Derek Buitenhuis a écrit : > Frankly, this is nothing nothing but an ad hominem attack. > > I am tired of it. This happens constantly, and the community > is always silent[1], and far too accepting of such toxic behavior. > > It has given me far too much unneeded stress and sourness. The > complete inability of the community to address such behavior and > individuals is appalling. > > I've had enough. I've already distanced myself from the Libav > community recently for similar behavior, and I will be doing > so for the FFmpeg community as well now. > > Both are toxic communities. As of this email, I am unsubscribing > from both ffmpeg-devel and libav-devel. > > I hope both communities enjoy their little out of touch bubbles. > > [1] http://ffmpeg.org/pipermail/ffmpeg-devel/2016-May/193990.html I will make no difficulty saying that I am too somewhat annoyed by Carl Eugen's attitude, and, if it had came to that, you would probably have my support overruling his objections, depending on the specifics of course. But your decision to put all the community in the same bag and throw it away is no more mature. People on virtual communities do not step in to help, this is the sad state of human nature. It can be explained, if not excused: nobody is "really" harmed (I hope we did not arrive to the points of harassment and death threats that have happened in some gaming communities), so nobody feels concerned enough to step in. Plus, nobody here have enough time. For example, my reaction to this thread was "I do not know anything about G.729, I have still 300+ messages to sift after a family week-end, delete without reading"; I only fell on this sub-thread by happenstance. As for your mail from last week, my reaction was "he's right, people who criticize merges are annoying, but I do not have anything interesting to say on the point and nobody likes a useless '+1'". Now you are threatening to leave I feel motivated enough to write something, even though I have a few professional deadlines soon, but I do not really know what to say. What would you want? What kind of answer would you have expected to your mail from last week? If you feel that some people contribute only useless comments, then announce that you will utterly disregard them and then do so. You have commit rights. Do you want moral support? Assume you have it! They are the unreasonable ones, not you, therefore you can assume that silence means that the people whose support you value agree with you. I have, in my early days in some communities, acquired anti-cronies who would tell me "shut up cockroach" at all time. It used to make me suffer, until I realized: I do not care what they think of me, and the other people on the community, the people who made the community valuable, did not either. Well, I do not know where to go from there. Except this: Carl Eugen, from now on, consider that I oppose to any patch that you would sent that is not correctly produced by git format-patch / send-email. Regards, -- Nicolas George signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, 18 May 2016 16:24:53 +0200 wm4wrote: > That's why it's important. But he keeps ignoring our requests to > change this, mostly because he disrespects us for working with his > sworn arch-enemy, Libav. comments like this are not helpful. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
Hi, On Wed, May 18, 2016 at 10:25 AM, compnwrote: > On Wed, 18 May 2016 16:12:40 +0200 > Paul B Mahol wrote: > > > Dana 18. 5. 2016. 16:05 osoba "compn" napisala je: > > > > > > On Wed, 18 May 2016 14:10:57 +0200 > > > Paul B Mahol wrote: > > > > > > > On 5/18/16, Carl Eugen Hoyos wrote: > > > > > Hi! > > > > > > > > > > Attached patch allows to mux raw G.729 as supported by our G.729 > > > > > demuxer. > > > > > > > > > > Please comment, Carl Eugen > > > > > > > > > > > > > Please attach actual patch with commit log message. > > > > > > commit message is in the subj of the email i thought. > > > > Even if that's true It's not enough. > > the commit message itself > "lavf/rawenc: Add a G.729 muxer" > > is deficient in some way? if you could, please expand your answer? We can't tell if the commit message includes a body (additional text) or not. Ronald ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, 18 May 2016 16:12:40 +0200 Paul B Maholwrote: > Dana 18. 5. 2016. 16:05 osoba "compn" napisala je: > > > > On Wed, 18 May 2016 14:10:57 +0200 > > Paul B Mahol wrote: > > > > > On 5/18/16, Carl Eugen Hoyos wrote: > > > > Hi! > > > > > > > > Attached patch allows to mux raw G.729 as supported by our G.729 > > > > demuxer. > > > > > > > > Please comment, Carl Eugen > > > > > > > > > > Please attach actual patch with commit log message. > > > > commit message is in the subj of the email i thought. > > Even if that's true It's not enough. the commit message itself "lavf/rawenc: Add a G.729 muxer" is deficient in some way? if you could, please expand your answer? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, 18 May 2016 10:05:41 -0400 compnwrote: > On Wed, 18 May 2016 14:10:57 +0200 > Paul B Mahol wrote: > > > On 5/18/16, Carl Eugen Hoyos wrote: > > > Hi! > > > > > > Attached patch allows to mux raw G.729 as supported by our G.729 > > > demuxer. > > > > > > Please comment, Carl Eugen > > > > > > > Please attach actual patch with commit log message. > > commit message is in the subj of the email i thought. > People often use git send-email, which puts the first line of the commit message into the email subject field. The main usefulness of proper patches is that we can actually see what commit message he's going to use. For example, compare http://ffmpeg.org/pipermail/ffmpeg-devel/2016-May/193698.html and https://github.com/FFmpeg/FFmpeg/commit/88a849c714c17ad80d411f68e6575dfa1c8e8358 They're both the same patch. But the message is very different. The mail is pretty detailed. It gives a proper explanation why this change is needed, a way to reproduce it, a link to the upstream bug report, and even some analysis about past behavior (including useful git hashes). The commit... contains nothing. The subject is useless and can be derived from the code changes. The debian bug reference isn't a link and has to be manually retrieved. If you're hunting for a regression, and pinpoint this commit as a cause for the regression, you will be very annoyed and you will waste time on trying to understand the issue and reproducing it. You could try finding the mail in the mailing list archive, but this is additional work too. If the commit message subject is even similar to the mail's subject (they could be very different). Last but not least, a proper git-format-patch is easier to apply. That's why it's important. But he keeps ignoring our requests to change this, mostly because he disrespects us for working with his sworn arch-enemy, Libav. Now you explain to me why we should tolerate this. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, May 18, 2016 at 01:32:13PM +, Carl Eugen Hoyos wrote: > Derek Buitenhuis gmail.com> writes: > > > I would agree, but for some reason Carl feels he is exempt > > from the FFmpeg developer rules. > > I should probably add that this is an interesting comment > coming from somebody who breaks FFmpeg with nearly every > commit and not only absolutely refuses to work on fixes but > even blocks fixes if others want to help him. can you all please return to a more polite and productive tone this is not a contest about escalating attacks i dont want attacks -> vote about banning X and then probably Y leaving if X isnt banned which would make the vote a X xor Y which is really stupid no matter which way it ends Thanks [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I know you won't believe me, but the highest form of Human Excellence is to question oneself and others. -- Socrates signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
Dana 18. 5. 2016. 16:05 osoba "compn"napisala je: > > On Wed, 18 May 2016 14:10:57 +0200 > Paul B Mahol wrote: > > > On 5/18/16, Carl Eugen Hoyos wrote: > > > Hi! > > > > > > Attached patch allows to mux raw G.729 as supported by our G.729 > > > demuxer. > > > > > > Please comment, Carl Eugen > > > > > > > Please attach actual patch with commit log message. > > commit message is in the subj of the email i thought. Even if that's true It's not enough. > > -compn > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, 18 May 2016 13:32:13 + (UTC) Carl Eugen Hoyoswrote: > Derek Buitenhuis gmail.com> writes: > > > I would agree, but for some reason Carl feels he is exempt > > from the FFmpeg developer rules. > > I should probably add that this is an interesting comment > coming from somebody who breaks FFmpeg with nearly every > commit and not only absolutely refuses to work on fixes but > even blocks fixes if others want to help him. He is exempt because those are merges from Libav. So > Please stop making such comments! right back at you. Besides you keep ignoring common conventions, such as sending git format-patches instead of bare patches. Maybe you are simply unable to learn basic things? ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
Dana 18. 5. 2016. 15:29 osoba "Carl Eugen Hoyos"napisala je: > > Paul B Mahol gmail.com> writes: > > > Please attach actual patch with commit log message. > > As soon as you give a helpful comment for the Babyphone patch;-) > Now it is official: I'm calling meeting to ban you from FFmpeg. We can't tolerate such attacks to other devs. > Carl Eugen > > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, 18 May 2016 14:10:57 +0200 Paul B Maholwrote: > On 5/18/16, Carl Eugen Hoyos wrote: > > Hi! > > > > Attached patch allows to mux raw G.729 as supported by our G.729 > > demuxer. > > > > Please comment, Carl Eugen > > > > Please attach actual patch with commit log message. commit message is in the subj of the email i thought. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, 18 May 2016 14:41:46 +0100 Derek Buitenhuiswrote: > On 5/18/2016 2:30 PM, Carl Eugen Hoyos wrote: > > Since you indicated lately that you are so terribly interested > > in the tone here: > > Please stop making such comments! > > It's a legitimate criticism. You refuse to follow the FFmpeg > developer rules of using git format-patch. carl is grandfathered in :P -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On 5/18/2016 2:32 PM, Carl Eugen Hoyos wrote: > I should probably add that this is an interesting comment > coming from somebody who breaks FFmpeg with nearly every > commit and not only absolutely refuses to work on fixes but > even blocks fixes if others want to help him. Frankly, this is nothing nothing but an ad hominem attack. I am tired of it. This happens constantly, and the community is always silent[1], and far too accepting of such toxic behavior. It has given me far too much unneeded stress and sourness. The complete inability of the community to address such behavior and individuals is appalling. I've had enough. I've already distanced myself from the Libav community recently for similar behavior, and I will be doing so for the FFmpeg community as well now. Both are toxic communities. As of this email, I am unsubscribing from both ffmpeg-devel and libav-devel. I hope both communities enjoy their little out of touch bubbles. [1] http://ffmpeg.org/pipermail/ffmpeg-devel/2016-May/193990.html Sincerely, - Derek ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On 5/18/2016 2:30 PM, Carl Eugen Hoyos wrote: > Since you indicated lately that you are so terribly interested > in the tone here: > Please stop making such comments! It's a legitimate criticism. You refuse to follow the FFmpeg developer rules of using git format-patch. - Derek ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
Derek Buitenhuis gmail.com> writes: [...] Since you indicated lately that you are so terribly interested in the tone here: Please stop making such comments! Carl Eugen ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
Derek Buitenhuis gmail.com> writes: > I would agree, but for some reason Carl feels he is exempt > from the FFmpeg developer rules. I should probably add that this is an interesting comment coming from somebody who breaks FFmpeg with nearly every commit and not only absolutely refuses to work on fixes but even blocks fixes if others want to help him. Carl Eugen ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
Paul B Mahol gmail.com> writes: > Please attach actual patch with commit log message. As soon as you give a helpful comment for the Babyphone patch;-) Carl Eugen ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On 5/18/2016 1:10 PM, Paul B Mahol wrote: > Please attach actual patch with commit log message. I would agree, but for some reason Carl feels he is exempt from the FFmpeg developer rules. - Derek ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On 5/18/16, Carl Eugen Hoyoswrote: > Hi! > > Attached patch allows to mux raw G.729 as supported by our G.729 demuxer. > > Please comment, Carl Eugen > Please attach actual patch with commit log message. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel