linux-kernel - Re: [GIT PULL] clockevents/clocksource: 3.12 fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 13 Nov 2013 14:53:05 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
cc:	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Ingo Molnar <mingo@...nel.org>,
	John Stultz <john.stultz@...aro.org>,
	Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [GIT PULL] clockevents/clocksource: 3.12 fixes

On Wed, 13 Nov 2013, Uwe Kleine-König wrote:
> On Tue, Nov 12, 2013 at 11:57:46PM +0100, Thomas Gleixner wrote:
> > The whole misery starts that you decided to play maintainer and grab
> > some patches from the mailinglist and then offering them via a pull
> > request to me and others. Finally you tricked Daniel to take them,
> >From my POV this isn't "playing maintainer". You stopped reacting on the
> issue and I thought I make it easier for you (and others) to handle the
> patches in case you didn't take because of being busy with other stuff.

Yes, I vanished for a few weeks because I was busy otherwise. Where is
the problem? The world was still turning and the fix was not a highly
critical issue.

And your "make it easier" thing is utter bullshit. It takes me less
time to apply a single patch from mail than pulling a tree and
verifying the commit.

Aside of that, core code goes always directly through me and not via
Daniel.

Dammit, there are established workflows and there is no reason, except
for a highly critical bug fix to circumvent them. And if such a
situation happens, then the correct thing is to resend the patch to
Andrew and Linus and explaining, why its critical and can't wait for
the lazy maintainer to reappear.

Me and others have observed your busybody behaviour often enough. It
does not really earn you trust and respect.

Just for the record: I'm not pulling anything from you and I'm not
going to pull a tree from my submaintainers which contains a merge
from you.

Thanks,

	tglx