linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>, Jiri Olsa <jolsa@redhat.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Stephane Eranian <eranian@google.com>,
	Don Zickus <dzickus@redhat.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL 00/10] perf/core improvements and fixes
Date: Wed, 9 Apr 2014 07:31:09 +0200	[thread overview]
Message-ID: <20140409053109.GA26139@gmail.com> (raw)
In-Reply-To: <CAM9d7ciP4tLUmR-soEKH3nf6=XC5evKGfuQW1fUGA8Z42U3xCg@mail.gmail.com>


* Namhyung Kim <namhyung@kernel.org> wrote:

> Hi Andi,
> 
> On Wed, Apr 9, 2014 at 4:50 AM, Andi Kleen <andi@firstfloor.org> wrote:
> > Jiri Olsa <jolsa@redhat.com> writes:
> >
> >> hi Ingo,
> >> please consider pulling
> >
> > So who actually maintains perf user space now?
> >
> > I have at least 4 perf user patchkits/bug fixes pending, but 
> > Arnaldo hasn't answered any email for weeks.

So a bit of background: sloppy, abusive contributors not willing to 
change get ignored after some time. For example Andi got such a bad 
track record in the x86 and perf space with me that all your mails go 
to /dev/null currently. (I only saw this one because Namhyung replied 
to it.)

Andi, as I explained it to you previously, if you want me to merge 
patches from you then you need to 1) improve the way you work 2) send 
it to someone who is willing to deal with you and sign off on it and 
forward it to me.

Seems like you managed to burn up your goodwill with Arnaldo as well. 
You need to find someone else willing to pay the expense of dealing 
with your passive-aggressive style.

Just a quick example of your abuse: for example you know it perfectly 
well that perf is well maintained, a simple 'git log tools/perf/' will 
tell you that there's a steady stream of patches going in and that 
perf contributors are busy.

Yet in this mail you actually lie about that: you pretend that you 
don't know that most Linux maintainers have trouble working with you, 
you pretend that perf is "unmaintained", you pretend that you don't 
know who is maintaining it, just to create unfair pressure on Arnaldo 
...

That kind of approach really sucks, and if you run out of people's 
patience with petty office tactics like that then you should not fault 
them, you should fault yourself.

Thanks,

	Ingo

  parent reply	other threads:[~2014-04-09  5:31 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 18:00 [GIT PULL 00/10] perf/core improvements and fixes Jiri Olsa
2014-04-08 18:00 ` [PATCH 01/10] perf tests: Add thread maps lookup automated tests Jiri Olsa
2014-04-08 18:01 ` [PATCH 02/10] perf top: Fix documentation of invalid -s option Jiri Olsa
2014-04-08 18:01 ` [PATCH 03/10] tools lib traceevent: Print event name when show warning if possible Jiri Olsa
2014-04-08 18:01 ` [PATCH 04/10] tools lib traceevent: Do not call warning() directly Jiri Olsa
2014-04-08 18:01 ` [PATCH 05/10] perf callchains: Disable unwind libraries when libelf isn't found Jiri Olsa
2014-04-08 18:01 ` [PATCH 06/10] perf kmem: Introduce --list-cmds for use by scripts Jiri Olsa
2014-04-08 18:01 ` [PATCH 07/10] perf mem: " Jiri Olsa
2014-04-08 18:01 ` [PATCH 08/10] perf lock: " Jiri Olsa
2014-04-08 18:01 ` [PATCH 09/10] perf sched: " Jiri Olsa
2014-04-08 18:01 ` [PATCH 10/10] MAINTAINERS: Change e-mail to kernel.org one Jiri Olsa
     [not found] ` <8738hnk3dg.fsf@tassilo.jf.intel.com>
     [not found]   ` <CAM9d7ciP4tLUmR-soEKH3nf6=XC5evKGfuQW1fUGA8Z42U3xCg@mail.gmail.com>
2014-04-09  5:31     ` Ingo Molnar [this message]
2014-04-10  7:36 ` [GIT PULL v2] perf/core improvements and fixes Jiri Olsa
  -- strict thread matches above, loose matches on Subject: below --
2017-08-16 20:20 [GIT PULL 00/10] " Arnaldo Carvalho de Melo
2017-08-17  7:45 ` Ingo Molnar
2017-05-03 13:58 Arnaldo Carvalho de Melo
2017-05-03 17:30 ` Ingo Molnar
2017-01-17 16:06 Arnaldo Carvalho de Melo
2017-01-18  9:09 ` Ingo Molnar
2016-12-07 16:53 Arnaldo Carvalho de Melo
2016-12-07 18:17 ` Ingo Molnar
2016-06-20 22:23 Arnaldo Carvalho de Melo
2016-06-21  2:18 ` Namhyung Kim
2016-06-21  3:11   ` Brendan Gregg
2016-06-21 10:08     ` Paolo Bonzini
2016-06-21 16:14       ` Arnaldo Carvalho de Melo
2016-05-25 21:34 Arnaldo Carvalho de Melo
2016-04-01 21:56 Arnaldo Carvalho de Melo
2016-04-06  6:47 ` Ingo Molnar
2016-02-16 20:34 Arnaldo Carvalho de Melo
2016-02-17  7:39 ` Ingo Molnar
2015-11-28  1:22 Arnaldo Carvalho de Melo
2015-11-28  9:50 ` Ingo Molnar
2015-11-29 13:16   ` Namhyung Kim
2015-08-28 18:06 Arnaldo Carvalho de Melo
2015-08-31  8:28 ` Ingo Molnar
2015-07-30 16:16 Arnaldo Carvalho de Melo
2015-07-31  8:04 ` Ingo Molnar
2015-07-31 13:30   ` Arnaldo Carvalho de Melo
2015-06-16 18:21 Arnaldo Carvalho de Melo
2015-01-29 20:23 Arnaldo Carvalho de Melo
2015-01-30 18:28 ` Ingo Molnar
2014-12-22 15:29 Arnaldo Carvalho de Melo
2014-09-26 20:19 Arnaldo Carvalho de Melo
2014-09-27  7:20 ` Ingo Molnar
2013-11-14 20:25 Arnaldo Carvalho de Melo
2013-11-15  6:38 ` Ingo Molnar
2013-11-11 20:22 Arnaldo Carvalho de Melo
2013-11-05 20:09 Arnaldo Carvalho de Melo
2013-11-06  5:31 ` Ingo Molnar
2013-09-02 20:56 Arnaldo Carvalho de Melo
2013-09-03  5:49 ` Ingo Molnar
2013-02-14 21:44 Arnaldo Carvalho de Melo
2013-02-15 15:39 ` Ingo Molnar
2011-12-20 19:18 Arnaldo Carvalho de Melo
2011-12-20 19:33 ` Ingo Molnar
2010-08-06  1:46 Arnaldo Carvalho de Melo
2010-08-06  7:00 ` Ingo Molnar

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=20140409053109.GA26139@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=andi@firstfloor.org \
    --cc=dzickus@redhat.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).