From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: "Luis Claudio R. Goncalves" <lclaudio@uudg.org>,
Ingo Molnar <mingo@elte.hu>,
linux-rt-users@vger.kernel.org
Subject: Re: [PATCH] Fixes spurious system load spikes in /proc/loadavgrt
Date: Sat, 18 Aug 2007 00:21:06 +0200 [thread overview]
Message-ID: <1187389266.7007.119.camel@chaos> (raw)
In-Reply-To: <1187386993.23789.92.camel@imap.mvista.com>
On Fri, 2007-08-17 at 14:43 -0700, Daniel Walker wrote:
> On Fri, 2007-08-17 at 23:37 +0200, Thomas Gleixner wrote:
>
> > You really start to annoy me. There was a detailed bug description and
> > the code defect is easy to see. If you neither have the interest nor the
> > time to look at the actual _trivial_ _self explaining_ patch, then
> > please look for some other playground to live out your wisenheimer airs
> > and graces.
>
> I'm not you, and you can't force your opinion of the code on someone
> else. _I_ don't think it was trivial .. I really couldn't care less if
> your annoyed or not ..
Why is it relevant that you are not me ?
I do not force my opinion on someone else, but I simply request that
you do not force _your_ rules based on your personal world view on
people who send _valid_ and _useful_ patches
Also you as the -rt expert who "releases" his own -rt queues should be
able to recognize the value and correctness of such a patch despite the
possibly enhanceable text description. If your only comment on such a
patch consist of your self defined nitpick rules, then you should go
back and read your own mails where you accused others of scaring off
developers instead of embracing them.
Keep this tone up and you are right on the way to make the second entry
of my kernel related kill file right behind the lonely dude who managed
to make it there in 10 years:
http://lkml.org/lkml/2007/4/30/157
> > > If your just going to start flames Thomas take it off list.
> >
> > Flames are only flames when they happen in public.
>
> Not really, but either way flames are _bad_ for business.
I don't have any business with you.
tglx
next prev parent reply other threads:[~2007-08-17 22:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 0:37 [PATCH] Fixes spurious system load spikes in /proc/loadavgrt Luis Claudio R. Goncalves
2007-08-17 3:58 ` Daniel Walker
2007-08-17 8:39 ` Thomas Gleixner
2007-08-17 16:24 ` Daniel Walker
2007-08-17 21:37 ` Thomas Gleixner
2007-08-17 21:43 ` Daniel Walker
2007-08-17 22:21 ` Thomas Gleixner [this message]
2007-08-17 22:43 ` Daniel Walker
2007-08-17 23:33 ` Thomas Gleixner
2007-08-23 15:33 ` Sven-Thorsten Dietrich
2007-08-23 15:51 ` Ingo Molnar
2007-08-23 15:57 ` Sven-Thorsten Dietrich
2007-08-23 16:13 ` Luis Claudio R. Goncalves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1187389266.7007.119.camel@chaos \
--to=tglx@linutronix.de \
--cc=dwalker@mvista.com \
--cc=lclaudio@uudg.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.