From: jimmy bahuleyan <knight.camelot@gmail.com>
To: Grozdan Nikolov <microchip@chello.be>
Cc: Bernd Petrovitsch <bernd@firmix.at>, linux-kernel@vger.kernel.org
Subject: Re: How innovative is Linux?
Date: Sun, 24 Jun 2007 00:24:48 +0530 [thread overview]
Message-ID: <467D6C78.3050101@gmail.com> (raw)
In-Reply-To: <200706232015.33527.microchip@chello.be>
Grozdan Nikolov wrote:
> On Saturday 23 June 2007 19:53, you wrote:
>> On Sat, 2007-06-23 at 14:17 +0200, Grozdan Nikolov wrote:
>> [...]
>>
>>> Please CC me as I'm not subscribe to this mailing list,
>> Perhaps you should change that and find most answers for yourself.
>>
>>> Thanks!
>> Thanks!
>>
>> Bernd
>
> Perhaps you should change your rude attitude towards people who are seeking
> for answers without actually looking for rants or flame-wars. If you have
> read my replies to Alan, you should know why I asked these questions.... To
> clarify something that might be incorrect or biased in the articles I've read
> so far... if you could tell me a better place to ask about Linux internal
> stuff, please tell me so......
>
well, i would say this - put yourself into the shoes of a kernel
developer who barely has time to keep track of the large volume of
development work, discussions, testing, etc. Then someone who claims to
be not a kernel developer, who isn't subscribed to the list comes along
and says 'there is _no_ innovation in the linux kernel'. What would your
reaction be?
I'm not a kernel developer myself, but i think there are lots of
resources on the internet where you can read watered down versions of
discussions happening on this list.
> willing to answer or clarify some things to a person who's just looking for
> the *correct* answers
>
Of course, everyone wants to learn from the gurus. But confronting them
in this way hardly seems the right way ;)
-jb
--
Tact is the art of making a point without making an enemy.
next prev parent reply other threads:[~2007-06-23 18:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 12:17 How innovative is Linux? Grozdan Nikolov
2007-06-23 14:43 ` Alan Cox
2007-06-23 15:22 ` Grozdan Nikolov
2007-06-23 15:46 ` Alan Cox
2007-06-23 16:12 ` Torsten Duwe
2007-06-23 16:19 ` Grozdan Nikolov
2007-06-23 16:42 ` Torsten Duwe
2007-06-23 16:54 ` Matthew Jacob
2007-06-23 17:30 ` jimmy bahuleyan
2007-06-23 17:49 ` Diego Calleja
2007-06-23 19:23 ` Alan Cox
2007-06-23 21:02 ` Al Viro
2007-06-23 22:13 ` Alan Cox
2007-06-23 18:12 ` Jan Engelhardt
2007-06-23 19:44 ` Alan Cox
2007-06-23 17:38 ` Benny Amorsen
2007-06-23 19:18 ` Jeffrey V. Merkey
2007-06-23 18:36 ` Grozdan Nikolov
2007-06-24 4:31 ` Rik van Riel
2007-06-23 22:02 ` Carlo Wood
2007-06-23 22:16 ` David Kane
[not found] ` <345c044f0706231513u46d870es6539bdf5797b305b@mail.gmail.com>
2007-06-23 22:27 ` Alan Cox
2007-06-25 9:39 ` Hiro Yoshioka
2007-06-25 22:57 ` Adrian Bunk
2007-06-24 21:36 ` Nikita Danilov
2007-06-23 18:02 ` Satyam Sharma
2007-06-23 18:17 ` Grozdan Nikolov
2007-06-23 17:53 ` Bernd Petrovitsch
2007-06-23 18:15 ` Grozdan Nikolov
2007-06-23 18:54 ` jimmy bahuleyan [this message]
2007-06-23 19:06 ` Grozdan Nikolov
2007-06-23 23:15 ` Jesper Juhl
2007-06-25 15:12 ` Lennart Sorensen
2007-06-25 15:15 ` Jan Engelhardt
2007-06-25 16:37 ` Randy Dunlap
2007-06-25 16:42 ` Jan Engelhardt
2007-06-25 17:51 ` jimmy bahuleyan
2007-06-26 12:26 ` Helge Hafting
2007-06-23 17:43 Al Boldi
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=467D6C78.3050101@gmail.com \
--to=knight.camelot@gmail.com \
--cc=bernd@firmix.at \
--cc=linux-kernel@vger.kernel.org \
--cc=microchip@chello.be \
/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;
as well as URLs for NNTP newsgroup(s).