From: Tomas Szepe <szepe@pinerecords.com>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: If you want kbuild 2.5, tell Linus
Date: Mon, 3 Jun 2002 16:36:34 +0200 [thread overview]
Message-ID: <20020603143634.GA15033@louise.pinerecords.com> (raw)
In-Reply-To: <3434.1023112731@ocs3.intra.ocs.com.au> <3CFB6D24.2090309@evision-ventures.com>
> Somehow I can't resist, but this sounds like the
> devfs and RaiserFS story again:
>
> - devfs claimed "It will solve all major/minor number problems".
> Well we still struggle to get over with them. But now we have to
> account for the intricacies of devfs in addition too.
>
> - RaiserFS "Trees rule the world".
> Well ext3 (no I don't care about inn server!) is faster
> XFS is better manegeable. The "mutable filesystem semantics" modules
> and what a not are nowehre in sight.
>
> Both projects which got included due to "public preasure".
With all respect, Martin, if you want to offend Keith Owens, you'd be
better off trying to find _real flaws_ in kbuild25, rather than raking
the old muck about devfs.
Please reread Keith's post and try to understand what "the kbuild25
problem" is about. For if there's one issue it's NOT about, it's the
system's incompetence or redundancy.
Another one, in trying to put down other people's work, you should prolly
at least take care to spell names correctly. And FYI, reiserfs has been
here as a real solution for over two years and has worked perfectly, unlike
certain other code. I'm getting sick of this macho attitude from someone
who throws shit at *others* while unable to get *their own* work done
properly.
T.
next prev parent reply other threads:[~2002-06-03 14:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 13:58 If you want kbuild 2.5, tell Linus Keith Owens
2002-06-03 13:20 ` Martin Dalecki
2002-06-03 14:36 ` Tomas Szepe [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 15:29 Wayne.Brown
2002-06-03 16:05 ` Mark Mielke
2002-06-03 17:24 ` Thunder from the hill
2002-06-03 17:33 Martin.Knoblauch
2002-06-03 17:48 ` Thunder from the hill
2002-06-04 7:04 Martin.Knoblauch
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
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=20020603143634.GA15033@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=dalecki@evision-ventures.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