From: Omkhar Arasaratnam <omkhar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] linux-2.6.12
Date: Sat, 18 Jun 2005 09:34:30 -0400 [thread overview]
Message-ID: <42B422E6.2090602@gentoo.org> (raw)
In-Reply-To: <42B3F713.1000108@gentoo.org>
Luca Barbato wrote:
>Kumba wrote:
>
>
>
>>I'm just stating this, because once reiserfs4 goes mainline (I believe
>>it's in -mm currently), we are bound to have users hitting various bumps
>>and ruts in the road using it, and if they file bugs to our bugzilla
>>that aren't related to patches we produce, then they'll likely wind up
>>closed as invalid and such. This saves the users time, and may get them
>>the answers they seek (or at least a resolution of some kind). It also
>>saves our bug-wranglers time by now having to deal with more invalid bugs.
>>
>>
>>
>
>We can always patch the problem in the g-s ^^
>
>Given reiserfs4 is around for enough time and lots of brave users tested
>it, it MAY be not so unstable. (still I like jfs and xfs more, and I use
>them just for transient data (large video and image processing tests and
>so on))
>
>
>
As a ppc64 arch and can officially state that reiser4fs is very unstable
under ppc64 as of the last time I checked, which was some where in the
2.6.12rc cycle plus mm patch.
That said, we're not RedHat. We ship as MANY features as we can and let
the user decide. I agree that it is valuable to get reiser4 testing done
up front. Eventually - some people will use it. Last I checked "I think
$FOO is stupid" wasn't a valid closure code in bugzilla ;-)
--
Omkhar Arasaratnam - Gentoo PPC64 Developer
omkhar@gentoo.org - http://dev.gentoo.org/~omkhar
Gentoo Linux / PPC64 Linux: http://ppc64.gentoo.org
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-06-18 13:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 4:22 [gentoo-dev] linux-2.6.12 Andrew Muraco
2005-06-18 4:50 ` Mike Frysinger
2005-06-18 4:52 ` Andrew Muraco
2005-06-18 5:05 ` Jason Wever
2005-06-18 6:03 ` Kumba
2005-06-18 6:04 ` Andrew Muraco
2005-06-18 6:26 ` Kumba
2005-06-18 10:27 ` Luca Barbato
2005-06-18 10:44 ` Jason Stubbs
2005-06-18 13:34 ` Omkhar Arasaratnam [this message]
2005-06-18 14:20 ` [gentoo-dev] linux-2.6.12 Duncan
2005-06-22 15:22 ` Duncan
2005-06-18 16:44 ` [gentoo-dev] linux-2.6.12 Daniel Drake
2005-06-18 20:47 ` Andrew Muraco
2005-06-19 23:12 ` Omkhar Arasaratnam
2005-06-20 17:00 ` Daniel Drake
2005-06-20 15:44 ` Chris Gianelloni
2005-06-18 5:05 ` Jason Stubbs
2005-06-18 5:53 ` Andrew Muraco
2005-06-18 6:03 ` Mike Frysinger
2005-06-18 6:21 ` Andrew Muraco
2005-06-18 6:28 ` Mike Frysinger
2005-06-18 6:31 ` Andrew Muraco
2005-06-18 15:04 ` Chris PeBenito
2005-06-18 7:54 ` Daniel Drake
2005-06-18 13:28 ` Omkhar Arasaratnam
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=42B422E6.2090602@gentoo.org \
--to=omkhar@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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