From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Christoph Lameter" <cl@linux-foundation.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, travis@sgi.com
Subject: Re: Git next: Second stage of cpu_alloc patches
Date: Wed, 5 Nov 2008 22:12:04 +0100 [thread overview]
Message-ID: <19f34abd0811051312o1fe733d8g4d0075aa7eefa964@mail.gmail.com> (raw)
In-Reply-To: <20081105082754.2d41f0d1.akpm@linux-foundation.org>
On Wed, Nov 5, 2008 at 5:27 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> We need to get alpha sorted out too. Frankly, if we can't get anyone to
> review/test/ack the alpha genirq conversion then I'd say merge it
> anyway. I'll make sure that it at least compiles.
Sounds like a bad strategy. What are these patches you're talking
about, and where can I find them?
I mean, isn't "merge anyway" the same as admitting defeat? I thought
we were going for 100% "review coverage".
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-11-05 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 2:56 Christoph Lameter
2008-11-05 3:52 ` Andrew Morton
2008-11-05 7:26 ` Stephen Rothwell
2008-11-05 7:52 ` Vegard Nossum
2008-11-05 13:59 ` Christoph Lameter
2008-11-05 13:54 ` Christoph Lameter
2008-11-05 16:27 ` Andrew Morton
2008-11-05 21:12 ` Vegard Nossum [this message]
2008-11-05 21:24 ` Andrew Morton
2008-11-05 23:58 ` Johannes Weiner
2008-11-06 0:54 ` Stephen Rothwell
2008-11-06 14:54 ` Christoph Lameter
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=19f34abd0811051312o1fe733d8g4d0075aa7eefa964@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=travis@sgi.com \
/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
all inboxes | Powered by JetHome®