Re: [FFmpeg-devel] possible farewell; dev policy clarification

2015-10-31 Thread Ganesh Ajjanagadde
On Sat, Oct 31, 2015 at 1:01 AM, Rostislav Pehlivanov wrote: > I agree with the others. There's quite a lot of noise on the ML and having > some of > your trivial patches (e.g. replacing functions with FFmpeg defined ones) > merged into > one would help to decrease it. Could be, but please then a

Re: [FFmpeg-devel] possible farewell; dev policy clarification

2015-10-30 Thread Rostislav Pehlivanov
I agree with the others. There's quite a lot of noise on the ML and having some of your trivial patches (e.g. replacing functions with FFmpeg defined ones) merged into one would help to decrease it. >Currently I am trying to get rid of a >lot of the last aspect to create a foundation for myself to

Re: [FFmpeg-devel] possible farewell; dev policy clarification

2015-10-30 Thread Ronald S. Bultje
Hi, On Fri, Oct 30, 2015 at 11:35 AM, Ganesh Ajjanagadde wrote: > Most, and perhaps all of them boil down to misunderstanding. This will > hopefully improve over time. I apologize to all who did not like > recent pushes from me. In fact, I can freely let go of my commit > access if these were de

Re: [FFmpeg-devel] possible farewell; dev policy clarification

2015-10-30 Thread Ganesh Ajjanagadde
On Fri, Oct 30, 2015 at 8:42 AM, Paul B Mahol wrote: > On 10/30/15, Ganesh Ajjanagadde wrote: >> Hi all, >> >> Apologies for the length of the email, but there is a lot of stuff I >> would like to cover due to my absence on IRC or other venues for "non >> patch related" discussion. >> >> There ha

Re: [FFmpeg-devel] possible farewell; dev policy clarification

2015-10-30 Thread Ganesh Ajjanagadde
On Fri, Oct 30, 2015 at 10:07 AM, Nicolas George wrote: > Hi. > > I am not on IRC either, so I can not comment on what happen there. I hope I > have not shown myself what you consider hostility on this list. I will try > to explain what I think may irritate people in your actions on this list. > >

Re: [FFmpeg-devel] possible farewell; dev policy clarification

2015-10-30 Thread Michael Niedermayer
On Fri, Oct 30, 2015 at 01:42:30PM +0100, Paul B Mahol wrote: > On 10/30/15, Ganesh Ajjanagadde wrote: [...] > > e) I have no personal interest in asm optimizations (to address a > > suggestion on IRC). I do appreciate the hard work there, it just does > > not appeal to me for reasons that I can a

Re: [FFmpeg-devel] possible farewell; dev policy clarification

2015-10-30 Thread Nicolas George
Hi. I am not on IRC either, so I can not comment on what happen there. I hope I have not shown myself what you consider hostility on this list. I will try to explain what I think may irritate people in your actions on this list. I will not comment on the issue of pushing without having addressed

Re: [FFmpeg-devel] possible farewell; dev policy clarification

2015-10-30 Thread Clément Bœsch
On Fri, Oct 30, 2015 at 07:34:29AM -0400, Ganesh Ajjanagadde wrote: [...] TL;DR Reviews are not meant to encourage, reviews are meant to find problems. A good review is a review where problems are found and pointed out. Sometimes, reviews mean suggesting way to find issues (which is then generall

Re: [FFmpeg-devel] possible farewell; dev policy clarification

2015-10-30 Thread Derek Buitenhuis
Hi, I'll chime in on a few points. On 10/30/2015 11:34 AM, Ganesh Ajjanagadde wrote: > 1. "Sloppy" patches - I tend to give more verbose commit messages to > explain rationale than many here. I also outlined why I did not post > benchmarks initially. I myself still think they are unnecessary and

Re: [FFmpeg-devel] possible farewell; dev policy clarification

2015-10-30 Thread Paul B Mahol
On 10/30/15, Ganesh Ajjanagadde wrote: > Hi all, > > Apologies for the length of the email, but there is a lot of stuff I > would like to cover due to my absence on IRC or other venues for "non > patch related" discussion. > > There has been a lot said and still being said regarding some patches >