From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
eranian@gmail.com, Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
Alexander van Heukelum <heukelum@mailshack.com>,
the arch/x86 maintainers <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: manual merge of the perfmon3 tree
Date: Wed, 26 Nov 2008 10:31:29 +0100 [thread overview]
Message-ID: <1227691889.4259.2871.camel@twins> (raw)
In-Reply-To: <20081126010022.63049908.akpm@linux-foundation.org>
On Wed, 2008-11-26 at 01:00 -0800, Andrew Morton wrote:
> On Wed, 26 Nov 2008 09:46:04 +0100 Ingo Molnar <mingo@elte.hu> wrote:
>
> > _Especially_ if
> > then the linux-next integrator also plays stupid about basic kernel
> > workflow questions ;-)
>
> He didn't. I suggested to Stephane and Stephen that we get this stuff
> into linux-next for a shot at 2.6.29 and that the collective 'we' make
> an extra effort to get perfmon over the hump and merged up.
>
> You missed that email, missed the presence of perfmon in linux-next
> and repeatedly chose to not review the perfmon patch series when it went
> past.
>
> So here we all are.
It just seems to me that CC-ing the intended 'we' at that point would
have saved a lot of grief.
Stuffing 2.3k lines of code in without the maintainers ACK is not
something we do each day, and I can understand them getting miffed about
that. I think every maintainer would consider such an action plain rude.
next prev parent reply other threads:[~2008-11-26 9:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 10:03 linux-next: manual merge of the perfmon3 tree Stephen Rothwell
2008-11-25 10:22 ` Ingo Molnar
2008-11-25 14:40 ` stephane eranian
2008-11-25 15:33 ` Ingo Molnar
2008-11-25 16:36 ` stephane eranian
2008-11-25 16:51 ` Ingo Molnar
2008-11-26 3:00 ` Stephen Rothwell
2008-11-26 3:33 ` Ingo Molnar
2008-11-26 7:06 ` Paul Mackerras
2008-11-26 7:16 ` Ingo Molnar
2008-11-26 8:32 ` stephane eranian
2008-11-26 8:46 ` Ingo Molnar
2008-11-26 9:00 ` Andrew Morton
2008-11-26 9:31 ` Peter Zijlstra [this message]
2008-11-26 10:21 ` Ingo Molnar
2008-11-25 10:39 ` Alexander van Heukelum
2008-11-25 15:19 ` stephane eranian
-- strict thread matches above, loose matches on Subject: below --
2008-11-26 4:24 H. Peter Anvin
2008-11-25 10:03 Stephen Rothwell
2008-11-07 8:42 Stephen Rothwell
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=1227691889.4259.2871.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=eranian@gmail.com \
--cc=heukelum@mailshack.com \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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