From: Timothy Miller <miller@techsource.com>
To: Hans Reiser <reiser@namesys.com>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"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 10:31:35 -0400 [thread overview]
Message-ID: <40C9C247.4070702@techsource.com> (raw)
In-Reply-To: <40C91DA0.6060705@namesys.com>
Hans Reiser wrote:
> This is all part of what responsible release management is about. I
> was the junior whiz kid in professional release management teams before
> starting Namesys. I listened to my elders and learned from them. My
> standards for professional conduct in this arena are higher than yours
> as a result of that.
> You are a bunch of young kids who lack professional experience in
> release management. That is ok, but don't get aggressive about it.
>
> I have no desire to pay for your mistakes, and as the official
> maintainer it is my responsibility to ensure that neither I nor the
> users pay for the mistakes of those who add bugs to stable branches
> instead of adding them to the development branches where they belong.
Don't get condescending. Immature people don't like to be told that
they are immature. :)
Anyhow, I agree with you. V3 should remain unchanged. If Linux wants
ReiserFS AND 4K stacks, they're going to have to wait for V4.
next prev parent reply other threads:[~2004-06-11 14:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 12:22 [STACK] >3k call path in reiserfs 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
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 [this message]
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=40C9C247.4070702@techsource.com \
--to=miller@techsource.com \
--cc=davej@redhat.com \
--cc=joern@wohnheim.fh-wedel.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.