From: Valdis.Kletnieks@vt.edu
To: debian developer <debiandev@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Scott Preece <sepreece@gmail.com>,
Krzysztof Halasa <khc@pm.waw.pl>,
"John Anthony Kazos Jr." <jakj@j-a-k-j.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 1/1] document Acked-by:
Date: Sat, 02 Jun 2007 15:34:49 -0400 [thread overview]
Message-ID: <7064.1180812889@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 02 Jun 2007 19:04:29 +0530." <f24d23310706020634p3f9f4187j577bea46df86ee5d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
On Sat, 02 Jun 2007 19:04:29 +0530, debian developer said:
> On 6/2/07, Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > It's quite common for experienced kernel developers to ack completely broken
> > patches.
>
> common!!
>
> is'nt that a bit too ...
Lots of code looks totally reasonable to a kernel coder, except it doesn't
actually work when run, or doesn't actually build for a common architecture.
Let's face it - if I hit a bug on my Dell Latitude in a -mm kernel, our
current depth of testers means that I'm probably the only person who's
likely to test the fix before it goes uptream to Linus as a "probably works".
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-06-02 19:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 2:09 akpm
2007-06-01 5:32 ` Valdis.Kletnieks
2007-06-01 6:10 ` H. Peter Anvin
2007-06-01 10:53 ` John Anthony Kazos Jr.
2007-06-01 19:27 ` Krzysztof Halasa
2007-06-01 19:37 ` Scott Preece
2007-06-01 20:00 ` Andrew Morton
2007-06-01 20:04 ` Andrew Morton
2007-06-02 13:34 ` debian developer
2007-06-02 17:13 ` Jan Engelhardt
2007-06-02 19:34 ` Valdis.Kletnieks [this message]
2007-06-01 22:10 ` Krzysztof Halasa
2007-06-01 22:17 ` H. Peter Anvin
2007-06-01 22:42 ` Krzysztof Halasa
2007-06-02 0:37 ` John Anthony Kazos Jr.
2007-06-02 0:56 ` Krzysztof Halasa
2007-06-02 1:36 ` Valdis.Kletnieks
2007-06-01 17:27 ` Valdis.Kletnieks
2007-06-01 17:35 ` Andrew Morton
2007-06-01 18:14 ` Dave Jones
2007-06-01 18:22 ` Andrew Morton
2007-06-01 18:28 ` Dave Jones
2007-06-02 17:17 ` Jan Engelhardt
2007-06-02 18:00 ` John Anthony Kazos Jr.
2007-06-02 19:07 ` Sam Ravnborg
2007-06-02 14:11 ` Adrian Bunk
2007-06-02 17:47 ` Andrew Morton
2007-06-02 17:55 ` Adrian Bunk
2007-06-03 0:23 ` Krzysztof Halasa
2007-06-03 2:57 ` Scott Preece
2007-06-03 4:06 ` Randy Dunlap
2007-06-03 4:15 ` Andrew Morton
2007-06-03 18:31 ` Scott Preece
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=7064.1180812889@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=debiandev@gmail.com \
--cc=hpa@zytor.com \
--cc=jakj@j-a-k-j.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=sepreece@gmail.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®