From: Miles Lane <miles@megapathdsl.net>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: kbuild 2.5 is ready for inclusion in the 2.5 kernel - take 3
Date: 17 May 2002 01:42:44 -0700 [thread overview]
Message-ID: <1021624966.10049.780.camel@turbulence.megapathdsl.net> (raw)
In-Reply-To: <20020517033056.GB4595@louise.pinerecords.com>
On Thu, 2002-05-16 at 20:30, Tomas Szepe wrote:
> > > Third and final attempt. Original sent on May 2, second mail sent on
> > > May 14, still no response from Linus.
> >
> > Linus is a bastard. Did you forget?
>
> This is getting ridiculous all right.
>
> Linus, what makes you ignore Keith's work?
>
> Would you tend to think he's worked on kbuild25 this long
> to end up having to send a linus-dammit-would-you-have-
> -a-look-at-last-i'm-not-going-to-keep-asking-forever msg?
>
> Sorry for a slightly offensive post; I can't stand to
> see such impoliteness.
Along the same lines, we have James Bottomly attempting to
get support for the NCR Voyager architecture added to the
kernel. His original submission post was sent 2001-12-23:
http://marc.theaimsgroup.com/?l=linux-kernel&m=100913508007485&w=2
The latest submission attempt was sent 2002-05-11:
http://marc.theaimsgroup.com/?l=linux-kernel&m=102115570805131&w=2
It seems to me that adding a new architecture probably doesn't
impact the rest of the kernel much, so I am not sure way
acceptance would be so long delayed. I have noticed that
there has been minimal feedback to James, which he appears
to have responded to quickly and well. I tend to think
that any tweaks needed could be accomplished as easily once
the code has been accepted into the kernel tree.
Is there some justification for the delay that I have somehow
overlooked?
Miles
next prev parent reply other threads:[~2002-05-17 8:43 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 22:42 Keith Owens
2002-05-17 0:10 ` Nicolas Pitre
2002-05-17 3:30 ` Tomas Szepe
2002-05-17 7:55 ` Russell King
2002-05-17 8:42 ` Miles Lane [this message]
2002-05-17 13:11 ` Dave Jones
2002-05-17 13:09 ` Denis Vlasenko
2002-05-17 8:17 ` Tomas Szepe
2002-05-17 13:39 ` Denis Vlasenko
2002-05-17 1:50 ` jeff millar
2002-05-17 2:04 ` Keith Owens
2002-05-17 2:26 ` Dave Jones
2002-05-17 7:11 ` Kenneth Johansson
2002-05-17 15:13 ` Nicolas Pitre
2002-05-17 15:19 ` Tomas Szepe
2002-05-17 15:42 ` Nicolas Pitre
2002-05-18 1:39 ` Keith Owens
2002-05-18 2:11 ` Nicolas Pitre
2002-05-18 2:19 ` Keith Owens
2002-05-18 22:14 ` Drivers.conf and kbuild-2.5 [Was: kbuild 2.5 is ready ...] Sam Ravnborg
2002-05-18 22:35 ` Dave Jones
2002-05-19 10:45 ` Sam Ravnborg
2002-05-17 18:19 ` kbuild 2.5 is ready for inclusion in the 2.5 kernel - take 3 Diego Calleja
2002-05-19 15:46 ` Pavel Machek
2002-05-17 14:21 Wayne.Brown
2002-05-17 17:37 ` Adam Kropelin
2002-05-17 18:00 ` Robert Love
2002-05-17 14:56 James Bottomley
2002-05-17 19:51 Wayne.Brown
2002-05-17 20:09 ` Dave Jones
2002-05-17 20:25 ` Diego Calleja
2002-05-18 13:15 ` Paul P Komkoff Jr
2002-05-17 20:53 Wayne.Brown
2002-05-17 21:14 ` Andrew Morton
2002-05-17 21:42 ` William Lee Irwin III
2002-05-17 22:16 ` Kai Germaschewski
2002-05-17 22:34 ` William Lee Irwin III
2002-05-17 22:40 ` Larry McVoy
2002-05-18 0:41 ` Oliver Xymoron
2002-05-17 22:09 ` Nicolas Pitre
2002-05-18 0:38 ` Oliver Xymoron
2002-05-17 22:59 Wayne.Brown
2002-05-17 23:14 ` Robert Love
2002-05-18 4:01 ` Horst von Brand
2002-05-18 12:57 ` Diego Calleja
2002-05-18 5:09 Wayne.Brown
2002-05-18 5:23 ` David Lang
2002-05-18 13:11 ` Diego Calleja
2002-05-18 6:05 Wayne.Brown
2002-05-18 16:50 ` John Weber
2002-05-18 10:25 Mike Galbraith
2002-05-18 17:32 ` Wayne.Brown
2002-05-18 18:11 ` Tomas Szepe
2002-05-18 21:15 ` DervishD
2002-05-20 4:31 ` Mike Fedyk
2002-05-20 5:09 ` Albert D. Cahalan
2002-05-20 5:18 ` Keith Owens
2002-05-20 14:29 ` Juan Quintela
2002-05-20 5:11 ` Keith Owens
2002-05-19 10:26 Mike Galbraith
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=1021624966.10049.780.camel@turbulence.megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
--cc=torvalds@transmeta.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®