public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Muraco <tuxp3@leetworks.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] linux-2.6.12
Date: Sat, 18 Jun 2005 16:47:00 -0400	[thread overview]
Message-ID: <42B48844.2000202@leetworks.com> (raw)
In-Reply-To: <42B44F6F.80202@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Daniel Drake wrote:

>Omkhar Arasaratnam wrote:
>
>>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 ;-)
>
>
>Then you have different views from the kernel project :)
>
>We and try and make our kernel (gentoo-sources) _more_ stable than the
>official Linux releases. We mainly stick to bug fixes decreed worthy by the
>upstream developers, etc. We never include patches when we know of problems
>that they will introduce.
>
>Daniel

i know this has been said before many many times, but i really can't
wait until i can see reiserfs4 in a "stable" kernel (vanilla or
gentoo) but i doubt that the gentoo-sources crew is going to budge
[whining]please.. USE flag'd reiser4? please pretty please[/whinning]

Anyways, I can understand the hesitence for the kernel project to add
things that have so many possibilties of problems like reiserfs4..

But for me its stable enough that I've only had to run reiserfsck
once, and that was right after i set it up, and i had a powerloss.. i
ended up just mkreiser4'ing and starting over because it was before i
even unpacked a stage..

Anyways, Sorry that this wasnt in gentoo-user,
Regards, Andrew
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCtIhAphOMdPLugR4RApBEAKDTV1G40VuPiP5OfVdc0YbezIZF8QCgn/sF
e9s+42bIyQ0e+J/4UXchN20=
=pqyn
-----END PGP SIGNATURE-----

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-06-18 20:49 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
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 [this message]
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=42B48844.2000202@leetworks.com \
    --to=tuxp3@leetworks.com \
    --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