From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: tj@kernel.org, mingo@elte.hu, linux-kernel@vger.kernel.org,
kyle@mcmartin.ca
Subject: Re: [GIT PULL] percpu for 2.6.31
Date: Thu, 18 Jun 2009 14:39:59 -0700 [thread overview]
Message-ID: <20090618143959.62858ef6.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.2.01.0906181421460.16802@localhost.localdomain>
On Thu, 18 Jun 2009 14:22:20 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Thu, 18 Jun 2009, Tejun Heo wrote:
> >
> > Please pull from percpu-for-linus git tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git for-linus
>
> I'm very unhappy with this kind of crap.
AFACIT none of these patches have ever been in linux-next. Half or
more of them turned up on the mailing list for the first time two days
ago and there's little evidence that anyone has even looked at them.
If this doesn't mean "you missed 2.6.31" then what does?
Yes, things like this can be messy and hard to develop and maintain
outside the merge window. We understand this. There are special
cases. But when this happens, let's talk about it and see what we can
do! Please let's not pretend that this is an ordinary old git merge
like all the others.
next prev parent reply other threads:[~2009-06-18 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 8:07 [GIT PULL] percpu for 2.6.31 Tejun Heo
2009-06-18 21:22 ` Linus Torvalds
2009-06-18 21:39 ` Andrew Morton [this message]
2009-06-18 22:43 ` Tejun Heo
2009-06-19 6:49 ` Ingo Molnar
2009-06-18 22:33 ` Tejun Heo
2009-06-18 22:45 ` Tejun Heo
2009-06-19 1:47 ` Tejun Heo
2009-06-19 5:39 ` Ingo Molnar
2009-06-19 19:39 ` Linus Torvalds
2009-06-19 21:08 ` 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=20090618143959.62858ef6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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