All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: linux-kernel@vger.kernel.org
Subject: Re: Reiser4 Inclusion
Date: Mon, 31 Jul 2006 00:02:30 +0200	[thread overview]
Message-ID: <44CD2C76.2030700@imap.cc> (raw)
In-Reply-To: <06Jul25.011533edt.35900@gpu.utcc.utoronto.ca>

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

On 25.07.2006 07:15, Chris Siebenmann wrote:
> You write:
> | [...] Therefore an attitude which says "go on developing that
> | code out-of-tree, it's not ready for inclusion yet" is in direct
> | contradiction with the foundations of the no-stable-API policy.
> 
>  I don't think that there's a contradiction, because I believe that what
> the kernel developers are saying in general can be rewritten as:
> 
> 	- we don't care about things that are deliberately kept
> 	  out of the kernel
> *and*	- we also don't care about code that does not meet quality
> 	  or relevance standards

Actually, that *isn't* what I read regularly in lkml. Most statements of
rejection by kernel developers do *not* read "we don't care about that,
go away", but "this needs work here and there before we will accept it",
which in a way is the opposite of "we don't care".

But I am growing tired of this discussion. I tried to help, and instead
drew fire myself. My own fault of course. I misjudged the situation and
the emotional content of the ongoing dispute. I will now keep my tongue.

Regards
Tilman

PS: I was forced to give this answer publicly because your given E-mail
address wouldn't accept my private mail answer. My apologies if this is
not what you wanted.

-- 
Tilman Schmidt                          E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]

       reply	other threads:[~2006-07-30 22:02 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <06Jul25.011533edt.35900@gpu.utcc.utoronto.ca>
2006-07-30 22:02 ` Tilman Schmidt [this message]
2006-07-17 22:34 Reiser4 Inclusion linux
  -- strict thread matches above, loose matches on Subject: below --
2006-07-17  3:02 Caleb Gray
2006-07-17  9:25 ` Arjan van de Ven
2006-07-17 11:48   ` Grzegorz Kulewski
2006-07-17 11:57     ` Alexander Gran
2006-07-17 14:06     ` Diego Calleja
2006-07-17 14:31       ` Grzegorz Kulewski
2006-07-17 15:51         ` Matthias Andree
2006-07-18  7:59           ` Jan Engelhardt
2006-07-18 20:47             ` Matthias Andree
2006-07-19  1:19               ` Joshua Hudson
2006-07-19  9:27               ` Tilman Schmidt
2006-07-19 11:00                 ` Krzysztof Halasa
2006-07-19 11:03                 ` Pekka Enberg
2006-07-19 15:32                   ` Tilman Schmidt
2006-07-19 19:04                     ` Valdis.Kletnieks
2006-07-19 19:12                       ` Tilman Schmidt
2006-07-19 20:09                         ` Valdis.Kletnieks
2006-07-19 22:36                           ` Tilman Schmidt
2006-07-19 20:29                       ` Jeff V. Merkey
2006-07-19 22:01                         ` Matthias Andree
2006-07-19 22:34                     ` Helge Hafting
2006-07-17 15:52         ` gmu 2k6
2006-07-17 15:57           ` Alexander Gran
2006-07-17 19:01         ` Horst von Brand
2006-07-17 15:13     ` Jeff Anderson-Lee
2006-07-17 15:13       ` Jeff Anderson-Lee
2006-07-17 15:56       ` Matthias Andree
2006-07-17 15:56         ` Matthias Andree
2006-07-17 20:48       ` Erik Mouw
2006-07-18  0:49         ` Jeff Dike
2006-07-18 11:43           ` Christoph Hellwig
2006-07-18 16:38           ` Bryan Henderson
2006-07-17  9:44 ` Patrick McFarland
2006-07-17 11:07 ` Diego Calleja
2006-07-17 14:38 ` Alex Riesen
2006-07-17 18:05 ` Valdis.Kletnieks
2006-07-18 23:10   ` Nix

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=44CD2C76.2030700@imap.cc \
    --to=tilman@imap.cc \
    --cc=linux-kernel@vger.kernel.org \
    /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.