mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: grundig <grundig@teleline.es>
To: Lexington Luthor <Lexington.Luthor@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiserFS?
Date: Sun, 16 Jul 2006 18:55:30 +0200 (added by postmaster@terra.es)	[thread overview]
Message-ID: <20060716190841.7392e0b2.grundig@teleline.es> (raw)
In-Reply-To: <e9dm0p$15s$1@sea.gmane.org>

El Sun, 16 Jul 2006 16:29:24 +0100,
Lexington Luthor <Lexington.Luthor@gmail.com> escribió:

> I am just saddened that kernel decisions are motivated by politics and a 
> personal dislike of Hans Reiser rather than technical merit. :(

You (and every reiser4 fan that FUDs against linux developers just because
he can't understand why reiser4 still is not in) are seriously missing the
point.

Nobody is oppossing that reiser4 gets into the main linux tree. Let me
remember you that Linux has already merged quite a lot of filesystems,
including a lot of them that don't even matter in the real world (BeFS,
minix, ADFS, AFFS, EFS, VXFS, qnx4fs, sysvfs, ncpfs, codafs. Let me
also remember you that we have had other relevant filesystems for year
(reiser3, XFS, JFS), and everybody is ok with them, nobody is planning
to kill anyone.

With this short panoramic view of Linux I find shocking that people
dares even to _suggest_ that linux don't want to include a filesystem
for "political reasons".

Just to point you how wrong you are, compare OCFS2 and GFS. Both of them
are clustering filesystems, being OCFS from Oracle and GFS from Redhat.
_Both_ filesystems have been asked to be included in the main tree. As for
today, only OCFS2 is in (since 2.6.16, after several reviews and after
fixing their code like everyone else). GFS still isn't in and seems to
need work, but you won't see to the GFS technical leader tell everybody
(like Hans has done here) that Linux politics don't allow GFS to go in.
Instead of wining, they just go back to work on their issues.

  reply	other threads:[~2006-07-17  4:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-16 12:45 reiserFS? ivo welch
2006-07-16 13:50 ` reiserFS? Matthias Andree
2006-07-16 15:29   ` reiserFS? Lexington Luthor
2006-07-16 16:55     ` grundig [this message]
2006-07-17  9:23       ` reiserFS? Arjan van de Ven
2006-07-17 16:32       ` reiserFS? Lexington Luthor
2006-07-17 14:56     ` reiserFS? Matthias Andree
2006-07-16 14:19 ` reiserFS? Joseph Le-Phan
2006-07-16 16:16 reiserFS? Xavier Roche
2006-07-16 16:28 ` reiserFS? Christian Trefzer
2006-07-16 16:56   ` reiserFS? Theodore Tso
2006-07-16 17:26     ` reiserFS? Lexington Luthor
2006-07-16 17:48       ` reiserFS? Theodore Tso
2006-07-16 17:46     ` reiserFS? Dr. David Alan Gilbert
2006-07-16 18:14       ` reiserFS? Theodore Tso
2006-07-17 15:01   ` reiserFS? Matthias Andree
2006-07-17 21:07   ` reiserFS? Helge Hafting

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=20060716190841.7392e0b2.grundig@teleline.es \
    --to=grundig@teleline.es \
    --cc=Lexington.Luthor@gmail.com \
    --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 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®