mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Hans Reiser <reiser@namesys.com>
Cc: Dave Jones <davej@redhat.com>, Chris Mason <mason@suse.com>,
	reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [STACK] >3k call path in reiserfs
Date: Fri, 11 Jun 2004 00:35:32 +0200	[thread overview]
Message-ID: <20040610223532.GB3340@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <40C79FE2.4040802@namesys.com>

On Wed, 9 June 2004 16:40:18 -0700, Hans Reiser wrote:
> >
> Forcing kernel developers to distort their coding to keep stack sizes 
> small is not a good idea, as it makes the whole kernel harder to code 
> for a not very compelling (for 99% of users, please argue with me if you 
> think it is otherwise) benefit.
> 
> I do not think I favor disturbing V3's stability for the sake of the 4k 
> stack option, but my mind is still open.

Apart from the fact that v3 appears to be safe on this front, your
perspective of kernel development doesn't seem to match that of most
developers.

o The kernel proper has no stable interface, it changes all of the
time.  Breaking peripheral kernel code (i.e. filesystems and device
drivers) with any change is not considered a problem.  If someone
cares about the peripheral code, it will get fixed.

o Noone has special rights to any code in the kernel.  You've accepted
the GPL and thereby given anyone the right to make changes to reiser3
and to distribute the changed code.  Active maintainership is usually
valued, but without that, noone is special.

It appears to me that most developers agree to the two point above,
but you have some problems with them, at least lately.  Am i wrong?

Jörn

-- 
When you close your hand, you own nothing. When you open it up, you
own the whole world.
-- Li Mu Bai in Tiger & Dragon

  reply	other threads:[~2004-06-10 22:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 12:22 Jörn Engel
2004-06-09 12:31 ` Chris Mason
2004-06-09 16:53   ` Chris Mason
2004-06-09 17:06     ` Hans Reiser
2004-06-09 17:15       ` Chris Mason
2004-06-09 18:04         ` Hans Reiser
2004-06-09 18:20           ` Dave Jones
2004-06-09 23:40             ` Hans Reiser
2004-06-10 22:35               ` Jörn Engel [this message]
2004-06-11  2:49                 ` Hans Reiser
2004-06-11  7:03                   ` Arjan van de Ven
2004-06-11 13:46                   ` Jörn Engel
2004-06-11 16:32                     ` Hans Reiser
2004-06-11 16:50                       ` Jörn Engel
2004-06-11 17:08                         ` Paul Wagland
2004-06-11 17:46                       ` Chris Mason
2004-06-11 18:07                         ` Hans Reiser
2004-06-11 14:31                   ` Timothy Miller
2004-06-11 14:42                     ` Jörn Engel
2004-06-09 17:28       ` Jörn Engel
2004-06-09 18:09         ` Hans Reiser
2004-06-09 18:34           ` Jörn Engel
2004-06-09 23:42             ` Hans Reiser
2004-06-11 13:49               ` Jörn Engel
2004-06-11 16:34                 ` Hans Reiser
2004-06-09 18:48           ` Chris Mason
2004-06-09 18:53             ` Jörn Engel
2004-06-09 23:44             ` Hans Reiser
2004-06-10  9:08           ` Vladimir Saveliev

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=20040610223532.GB3340@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-dev@namesys.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®