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 15:46:21 +0200	[thread overview]
Message-ID: <20040611134621.GA3633@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <40C91DA0.6060705@namesys.com>

On Thu, 10 June 2004 19:49:04 -0700, Hans Reiser wrote:
> Jörn Engel wrote:
> 
> >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?
> 
> 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.

Well, this ain't OpenBSD.  They have a strict 6month release schedule,
so your type of development works just fine for them.  Linux has
something like a very relaxed 24month+ release "schedule", which is
far too long for some people.  As a result, the Linux "stable" kernel
is a lot less stable than the OpenBSD one.

But long release cycles also have their advantages and - most
important - they work with Linus.  So effectively, we all have to
accept them and deal with the consequenses.  I really understand and
partially share your doubts, but what does it help? ;)

Jörn

-- 
You can't tell where a program is going to spend its time. Bottlenecks
occur in surprising places, so don't try to second guess and put in a
speed hack until you've proven that's where the bottleneck is.
-- Rob Pike

  parent reply	other threads:[~2004-06-11 13:46 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
2004-06-11  2:49                 ` Hans Reiser
2004-06-11  7:03                   ` Arjan van de Ven
2004-06-11 13:46                   ` Jörn Engel [this message]
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=20040611134621.GA3633@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®