From: Mark Mielke <mark@mark.mielke.cc>
To: Wayne.Brown@altec.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: If you want kbuild 2.5, tell Linus
Date: Mon, 3 Jun 2002 12:05:54 -0400 [thread overview]
Message-ID: <20020603120554.A29569@mark.mielke.cc> (raw)
In-Reply-To: <86256BCD.0055567F.00@smtpnotes.altec.com>
On Mon, Jun 03, 2002 at 10:29:10AM -0500, Wayne.Brown@altec.com wrote:
> Keith Owens <kaos@ocs.com.au> wrote:
> >It is a sad day when a fully tested and documented system that is
> >faster and, above all, more accurate, cannot get into the kernel.
> >Linus is judging kbuild 2.5 on its popularity and on personalities, not
> >on its technical merits.
> Right, make Linus do what you want by impugning his technical
> judgment, calling him a liar, and asking people to flood his mailbox
> with complaints. Sure, THAT will work.
It is still unfortunate that all contributions, especially larger scale
ones, cannot be openly accepted and embraced. It isn't as if the change
is overly invasive... if both system can operate in parallel, the impact
is significantly less.
Alas, we have these things called precidents and processes that attempt to
hone the quality of releases at the cost of potential productivity.
Keith: I do not think Linus is discouraging kbuild 2.5 due to popularity
or personalities. I suspect he is discouraging it due to a healthy fear
of the precident that it would set, as well as the chance that it would
require a great deal more work and you and your collaborators all get hit
by a bus ( or get a life? :-) ) tomorrow morning.
I'm not certain where the line is for 'breaking the change up', such that
the effort does not become substantially more, but the requirement for the
line has been decreed.
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2002-06-03 16:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 15:29 If you want kbuild 2.5, tell Linus Wayne.Brown
2002-06-03 16:05 ` Mark Mielke [this message]
2002-06-03 17:24 ` Thunder from the hill
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 21:01 Jesse Pollard
2002-06-06 21:36 ` Tomas Szepe
2002-06-10 21:43 ` Bill Davidsen
2002-06-07 1:39 ` Mark Mielke
2002-06-07 15:31 ` Thunder from the hill
2002-06-08 15:51 ` David Woodhouse
2002-06-08 15:54 ` Thunder from the hill
2002-06-04 7:04 Martin.Knoblauch
2002-06-03 17:33 Martin.Knoblauch
2002-06-03 17:48 ` Thunder from the hill
2002-06-03 13:58 Keith Owens
2002-06-03 13:20 ` Martin Dalecki
2002-06-03 14:36 ` Tomas Szepe
2002-06-03 14:15 ` Daniel Phillips
2002-06-03 17:51 ` Austin Gonyou
2002-06-03 22:10 ` Diego Calleja
2002-06-03 22:24 ` John Alvord
2002-06-03 22:34 ` Thunder from the hill
2002-06-03 23:10 ` Diego Calleja
2002-06-04 1:26 ` Daniel Phillips
2002-06-06 19:31 ` Kai Henningsen
2002-06-06 20:56 ` Tom Rini
2002-06-07 0:30 ` Daniel Phillips
2002-06-07 15:29 ` Thunder from the hill
2002-06-03 14:33 ` Nicolas Pitre
2002-06-03 15:27 ` Peter Wächtler
2002-06-03 16:09 ` Nicolas Pitre
2002-06-03 14:54 ` Daniel Phillips
2002-06-03 17:26 ` Olivier Galibert
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=20020603120554.A29569@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=Wayne.Brown@altec.com \
--cc=linux-kernel@vger.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