From: Hans Reiser <reiser@namesys.com>
To: marcel@hilzinger.hu
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Reiserfs developers mail-list <reiserfs-dev@namesys.com>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: 2.6.9-mm1
Date: Sat, 23 Oct 2004 13:28:50 -0700 [thread overview]
Message-ID: <417ABF02.4030705@namesys.com> (raw)
In-Reply-To: <1078.217.232.234.250.1098558101.squirrel@florka.hu>
Hilzinger Marcel wrote:
>
>Too late, perhaps... SuSE Linux 9.2 will contain reiser4 (at least the
>beta testversions did). It cannot be set up via YaST during installation,
>
>
which makes its user base pretty small. 9.3 is where we will probably
get a lot of users. Probably more bugs will get found by the SuSE QA
team in the next few weeks though, and that should help us.
The one I am wanting to precede regarding shipping is Lindows where we
will be the default. Reiser4 is pretty stable now, but if we got into
the kernel now we'd have a few weeks of bug finding before they ship,
and I just bet there will be a few bugs found as a result (not frequent
ones, but....) that several of their users would be happy to not hit.
The official kernel has the advantage of a far faster test and fix time
cycle than a distro, and has more sophisticated users. The reason for
features going into distros first is not technical, and sad.
Hans
next prev parent reply other threads:[~2004-10-23 20:28 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 10:20 2.6.9-mm1 Andrew Morton
2004-10-22 10:39 ` 2.6.9-mm1 Christoph Hellwig
2004-10-22 10:54 ` 2.6.9-mm1 Andrew Morton
2004-10-22 11:08 ` 2.6.9-mm1 Christoph Hellwig
2004-10-22 17:26 ` 2.6.9-mm1 Hans Reiser
2004-10-22 19:34 ` 2.6.9-mm1 Roman Zippel
2004-10-27 11:19 ` 2.6.9-mm1 Christoph Hellwig
2004-10-22 15:54 ` 2.6.9-mm1 Chris Wright
2004-10-22 12:23 ` 2.6.9-mm1 Eyal Lebedinsky
2004-10-22 19:26 ` 2.6.9-mm1 Adrian Bunk
2004-10-22 13:39 ` 2.6.9-mm1: pc_debug multiple definitions Adrian Bunk
2004-10-22 23:07 ` Russell King
2004-10-24 3:41 ` Luis R. Rodriguez
2004-10-24 9:33 ` Adrian Bunk
2004-10-24 10:05 ` Luis R. Rodriguez
2004-10-22 13:43 ` [patch] 2.6.9-mm1: usb/serial/console.c compile error Adrian Bunk
2004-10-22 18:08 ` Greg KH
2004-10-22 13:50 ` 2.6.9-mm1: timer_event multiple definition Adrian Bunk
2004-10-22 15:24 ` Christoph Lameter
2004-10-22 19:16 ` Adrian Bunk
2004-10-22 19:21 ` Christoph Lameter
2004-10-25 23:07 ` George Anzinger
2004-10-25 23:32 ` Christoph Lameter
2004-10-22 13:59 ` [patch] 2.6.9-mm1: ISDN hisax_fcpcipnp.c: kill unused variable Adrian Bunk
2004-10-22 15:30 ` 2.6.9-mm1 Jason Baron
2004-10-22 17:24 ` 2.6.9-mm1 Hans Reiser
2004-10-23 19:01 ` 2.6.9-mm1 Hilzinger Marcel
2004-10-23 19:39 ` 2.6.9-mm1 Andrew Morton
2004-10-23 19:49 ` 2.6.9-mm1 Jan Engelhardt
2004-10-24 17:42 ` 2.6.9-mm1 Alex Zarochentsev
2004-10-23 20:28 ` Hans Reiser [this message]
2004-10-24 14:41 ` 2.6.9-mm1 Dr. Giovanni A. Orlando
2004-10-24 14:41 ` 2.6.9-mm1 Clifford Beshers
2004-10-24 14:45 ` 2.6.9-mm1 Con Kolivas
2004-10-24 14:54 ` 2.6.9-mm1 Clifford Beshers
2004-10-25 19:52 ` 2.6.9-mm1 Bill Davidsen
2004-10-22 21:06 ` 2.6.9-mm1 (compile stats) John Cherry
2004-10-22 22:22 ` 2.6.9-mm1 Chuck Harding
2004-10-24 18:00 ` 2.6.9-mm1 john cooper
2004-10-25 21:24 ` 2.6.9-mm1 Chuck Harding
2004-10-23 0:12 ` pdc202xx_old broke boot [was Re: 2.6.9-mm1] J.A. Magallon
2004-10-23 0:21 ` Andrew Morton
2004-10-23 0:22 ` J.A. Magallon
2004-10-23 0:34 ` Bartlomiej Zolnierkiewicz
2004-10-27 22:19 ` [PATCH] " J.A. Magallon
2004-10-27 22:42 ` Bartlomiej Zolnierkiewicz
2004-10-23 0:13 ` 2.6.9-mm1 Dominik Karall
2004-10-23 10:37 ` 2.6.9-mm1 Gerd Knorr
2004-10-23 0:44 ` [patch] 2.6.9-mm1: dvb-dibusb.c: remove unused code Adrian Bunk
2004-10-23 10:48 ` Patrick Boettcher
2004-10-23 7:22 ` 2.6.9-mm1 Avuton Olrich
2004-10-23 16:59 ` 2.6.9-mm1 Markus Törnqvist
2004-10-23 22:03 ` 2.6.9-mm1 Kasper Sandberg
2004-10-25 19:54 ` 2.6.9-mm1 Bill Davidsen
2004-10-23 9:08 ` 2.6.9-mm1 Alexander Nyberg
2004-10-24 8:49 ` 2.6.9-mm1 Andrew Morton
2004-10-23 12:06 ` 2.6.9-mm1 Dominik Karall
2004-10-23 14:37 ` 2.6.9-mm1 Adrian Bunk
2004-10-23 15:55 ` 2.6.9-mm1 Hans Reiser
2004-10-23 16:57 ` 2.6.9-mm1 Markus Törnqvist
2004-10-24 2:37 ` 2.6.9-mm1 David Masover
2004-10-24 0:47 ` 2.6.9-mm1 Jan Engelhardt
2004-10-24 5:14 ` 2.6.9-mm1 Hans Reiser
2004-10-24 19:40 ` 2.6.9-mm1 David Masover
2004-10-25 20:07 ` 2.6.9-mm1 Bill Davidsen
2004-10-25 0:12 ` 2.6.9-mm1 J.A. Magallon
2004-10-25 11:47 ` 2.6.9-mm1 Arjan van de Ven
2004-10-25 22:31 ` 2.6.9-mm1 Randy.Dunlap
2004-10-25 22:56 ` 2.6.9-mm1 Andrew Morton
2004-10-25 23:14 ` 2.6.9-mm1 Randy.Dunlap
2004-10-25 23:47 ` 2.6.9-mm1 Andrew Morton
2004-10-25 23:36 ` 2.6.9-mm1 Randy.Dunlap
2004-10-26 1:34 ` 2.6.9-mm1 Bartlomiej Zolnierkiewicz
2004-10-26 3:04 ` 2.6.9-mm1 Randy.Dunlap
2004-10-26 15:48 ` 2.6.9-mm1 Randy.Dunlap
2004-10-26 16:40 ` 2.6.9-mm1 Bartlomiej Zolnierkiewicz
2004-10-26 20:01 ` 2.6.9-mm1 Randy.Dunlap
2004-10-26 6:49 ` 2.6.9-mm1 Nigel Cunningham
2004-10-26 17:58 ` 2.6.9-mm1 Alexander Nyberg
2004-10-26 20:19 ` 2.6.9-mm1 Andrew Morton
2004-10-31 4:17 ` 2.6.9-mm1 A little build system bug I guess Pedro Larroy
2004-10-31 8:10 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2004-10-22 20:32 2.6.9-mm1 Matthieu Castet
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=417ABF02.4030705@namesys.com \
--to=reiser@namesys.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@hilzinger.hu \
--cc=reiserfs-dev@namesys.com \
--cc=reiserfs-list@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;
as well as URLs for NNTP newsgroup(s).