From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Marc Perkel <mperkel@yahoo.com>
Cc: Brennan Ashton <comphappy@gmail.com>, Nix <nix@esperi.org.uk>,
Al Viro <viro@ftp.linux.org.uk>,
Kyle Moffett <mrmacman_g4@mac.com>,
Phillip Susi <psusi@cfl.rr.com>,
Michael Tharp <gxti@partiallystapled.com>,
LKML Kernel <linux-kernel@vger.kernel.org>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: Thinking outside the box on file systems
Date: Mon, 20 Aug 2007 17:26:33 +0200 [thread overview]
Message-ID: <46C9B2A9.1010904@aitel.hist.no> (raw)
In-Reply-To: <465458.84259.qm@web52505.mail.re2.yahoo.com>
Marc Perkel wrote:
> What's the point? People are openly hostile to new
> ideas here. I started out nice and laid out my ideas
> and you have a bunch of morons who attack anything
> new.
People here are not hostile to any new idea. They are
generally hostile to anyone who suggest some
"improvement" that he wants others to actually implement.
Because that is acting like a boss, and you're not the boss here.
Also - what do you expect when you bring an idea and say
"well, don't look at what might go wrong, that's just
limitations of the existing parts of linux?"
Sure, everybody can overlook how your ideas don't fit into
current linux - but then they have nothing more to say.
What people here do is to look at new ideas/patches, and
point out problems with them. When there are no more
problems left, the patch is applied and linux improves.
If we're not to point out problems with your ideas, then
they can't be used in linux. That is not hostility, but how
linux development works.
Mostly people try to save you from doing unnecessary work -
so you don't go and implement a flawed filesystem that
will be rejected immediately when you show up with the patch.
Shooting down bad ideas saves tremendous amounts of work,
killing an idea at the discussion stage means the idea never
got to the much more labor-intensive implementation stage.
This don't mean that all new ideas are killed, only the bad ones.
If you want your ideas accepted, you'll have to come up
with something that isn't flawed, that is well planned, not
just a bunch of "well - we could do *that* perhaps" but then
it turns out that *that* idea was flawed as well.
Helge Hafting
Helge Hafting
next prev parent reply other threads:[~2007-08-20 15:30 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 22:45 Marc Perkel
2007-08-14 22:51 ` alan
2007-08-15 13:02 ` Michael Tharp
2007-08-15 13:30 ` Lennart Sorensen
2007-08-15 13:53 ` Kyle Moffett
2007-08-15 15:14 ` Michael Tharp
2007-08-15 16:36 ` Marc Perkel
2007-08-15 17:17 ` Kyle Moffett
2007-08-15 17:30 ` Marc Perkel
2007-08-15 18:22 ` Craig Ruff
2007-08-15 20:35 ` Marc Perkel
2007-08-16 11:27 ` Helge Hafting
2007-08-15 16:02 ` Marc Perkel
2007-08-15 16:57 ` Valdis.Kletnieks
2007-08-15 17:09 ` Marc Perkel
2007-08-15 17:22 ` Kyle Moffett
2007-08-15 17:34 ` Marc Perkel
2007-08-18 23:27 ` Alan
2007-08-18 23:26 ` Alan
2007-08-19 2:03 ` david
2007-08-19 2:57 ` Al Viro
2007-09-01 23:20 ` Oleg Verych
2007-08-15 19:20 ` Lennart Sorensen
2007-08-16 23:12 ` H. Peter Anvin
2007-08-15 16:58 ` Kyle Moffett
2007-08-15 17:19 ` Marc Perkel
2007-08-15 17:37 ` Kyle Moffett
2007-08-15 17:59 ` Marc Perkel
2007-08-15 19:26 ` Lennart Sorensen
2007-08-15 20:11 ` Kyle Moffett
2007-08-15 20:44 ` Marc Perkel
2007-08-15 21:04 ` Lennart Sorensen
2007-08-16 11:42 ` Helge Hafting
2007-08-16 12:09 ` linux-os (Dick Johnson)
2007-08-15 17:34 ` Phillip Susi
2007-08-15 17:53 ` Kyle Moffett
2007-08-15 18:05 ` Marc Perkel
2007-08-15 18:14 ` Kyle Moffett
2007-08-15 20:20 ` Marc Perkel
2007-08-15 20:43 ` Phillip Susi
2007-08-15 20:50 ` Marc Perkel
2007-08-15 21:20 ` Valdis.Kletnieks
2007-08-15 22:48 ` Marc Perkel
2007-08-16 3:42 ` Valdis.Kletnieks
2007-08-15 20:38 ` Phillip Susi
2007-08-15 21:17 ` Kyle Moffett
2007-08-15 22:14 ` Phillip Susi
2007-08-16 4:44 ` Kyle Moffett
2007-08-16 15:09 ` Phillip Susi
2007-08-16 15:29 ` Valdis.Kletnieks
2007-08-16 17:28 ` Phillip Susi
2007-08-16 17:31 ` Valdis.Kletnieks
2007-08-16 22:03 ` Phillip Susi
2007-08-16 23:17 ` Kyle Moffett
2007-08-17 4:24 ` Marc Perkel
2007-08-17 4:52 ` Valdis.Kletnieks
2007-08-17 15:19 ` Phillip Susi
2007-08-17 15:39 ` Valdis.Kletnieks
2007-08-17 19:01 ` Phillip Susi
2007-08-18 5:48 ` Kyle Moffett
2007-08-18 16:45 ` Marc Perkel
2007-08-18 18:19 ` Al Viro
2007-08-19 4:07 ` Marc Perkel
2007-08-20 7:05 ` Nix
2007-08-20 7:47 ` Brennan Ashton
2007-08-20 11:18 ` Marc Perkel
2007-08-20 13:32 ` linux-os (Dick Johnson)
2007-08-20 15:25 ` Lennart Sorensen
2007-08-20 15:26 ` Helge Hafting [this message]
2007-08-20 19:52 ` Nix
2007-08-20 16:21 ` [OT] " Randy Dunlap
2007-08-20 16:20 ` Xavier Bestel
2007-08-20 14:29 ` Phillip Susi
2007-08-20 15:13 ` Lennart Sorensen
2007-08-20 14:24 ` Phillip Susi
2007-08-15 22:40 ` Marc Perkel
2007-08-15 17:54 ` Marc Perkel
2007-08-15 17:02 ` Marc Perkel
2007-08-15 17:30 ` Michael Tharp
2007-08-15 17:51 ` Marc Perkel
2007-08-15 20:02 ` Yakov Lerner
2007-08-15 7:49 Tim Tassonis
2007-08-15 18:23 Brian Wheeler
2007-08-20 11:54 Tim Tassonis
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=46C9B2A9.1010904@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=comphappy@gmail.com \
--cc=gxti@partiallystapled.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=mperkel@yahoo.com \
--cc=mrmacman_g4@mac.com \
--cc=nix@esperi.org.uk \
--cc=psusi@cfl.rr.com \
--cc=viro@ftp.linux.org.uk \
--cc=viro@zeniv.linux.org.uk \
/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®