>> I am trying to improve various open issues also in Linux source files.
>>
> That the fact that you see issues (in these particular cases) while
> others do not
I guess that the discussed "story" affects more challenges in communication
and different opinions about where to invest software devel
On 23 September 2016 at 09:50, SF Markus Elfring
wrote:
>> Markus, please contact the list in advance in future before posting a bunch
>> of patches that don't fix any problems.
>
> I am trying to improve various open issues also in Linux source files.
>
That the fact that you see issues (in these
> Markus, please contact the list in advance in future before posting a bunch
> of patches that don't fix any problems.
I am trying to improve various open issues also in Linux source files.
Unfortunately, some of the proposed changes might not fit to your software
development attention at the mo
> I will refrain from merging any more style/checkpatch/"code cleanup"
> patches from Markus until we start getting real, tested, bug fixes.
Can such a kind of feedback be also interpreted in the way that you insist
to keep some weaknesses which I tried to point in the Linux source code out
for an
>> Would you like to discuss the statistics for my failure (or success) rate
>> a bit more so that involved issues can be clarified in a constructive way?
>
> It should be that you target 20 bug fixes for each new regression
> that you add.
How do you think about to clarify any concrete "regressi
On 23 September 2016 at 17:25, Sean Paul wrote:
> On Thu, Sep 22, 2016 at 1:24 PM, Dan Carpenter
> wrote:
>> On Thu, Sep 22, 2016 at 03:11:25PM +0200, SF Markus Elfring wrote:
>>> > If you restricted yourself to fixing bugs only then you would maybe fix
>>> > more
>>> > bugs than you introduce
On Thu, Sep 22, 2016 at 1:24 PM, Dan Carpenter wrote:
> On Thu, Sep 22, 2016 at 03:11:25PM +0200, SF Markus Elfring wrote:
>> > If you restricted yourself to fixing bugs only then you would maybe fix
>> > more
>> > bugs than you introduce but as it you are making the kernel worse.
>>
>> Would you
On Thu, Sep 22, 2016 at 03:11:25PM +0200, SF Markus Elfring wrote:
> > If you restricted yourself to fixing bugs only then you would maybe fix more
> > bugs than you introduce but as it you are making the kernel worse.
>
> Would you like to discuss the statistics for my failure (or success) rate
>
On Do, 2016-09-22 at 19:16 +0200, SF Markus Elfring wrote:
> > For starters make sure the patches land actually on the list.
>
> How do you think about to take another look at this update suggestion
> also by the usual archive interfaces?
>
> * https://patchwork.kernel.org/patch/9344521/
>
> *
> For starters make sure the patches land actually on the list.
How do you think about to take another look at this update suggestion
also by the usual archive interfaces?
* https://patchwork.kernel.org/patch/9344521/
*
https://lkml.kernel.org/r/
> Only the cover letter arrived here.
Would y
On Do, 2016-09-22 at 15:11 +0200, SF Markus Elfring wrote:
> > Guys, please stop accepting patches from Markus!
>
> I would appreciate a bit more explanation for this request.
For starters make sure the patches land actually on the list.
Only the cover letter arrived here.
cheers,
Gerd
> Guys, please stop accepting patches from Markus!
I would appreciate a bit more explanation for this request.
> Markus, you always introduce bugs.
I find the wording "always" exaggerated.
It can also happen that I make another programming mistake occasionally.
> I have asked you over and ov
12 matches
Mail list logo
