From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] grub reiser4
Date: Mon, 03 Oct 2005 09:09:09 -0400 [thread overview]
Message-ID: <1128344949.6692.22.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <4340AC1E.8050103@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]
On Sun, 2005-10-02 at 22:57 -0500, Mike Doty wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Mike Frysinger wrote:
> | On Thursday 29 September 2005 02:10 pm, Chris Bainbridge wrote:
> |
> |>I was wondering if there's any chance of having the reiser4 patch for
> |>grub (or even the whole grub-reiser4 distfile) added to the ebuild.
> |>There are various bugs where people have posted patches for 0.96x
> |>ebuilds which were never added and the bugs have been WONTFIXed or
> |>left dangling. I've been using grub+reiser4 for about 9 months now
> |>with no problems. The last reason I heard it wouldn't be added was
> |>that no kernels in portage support it; I believe that's not true
> |>anymore, at least mm-sources has reiser4.
> |
> |
> | i'll ask a few devs how they feel about it before i commit it
> | -mike
> I'd prefer if the patch was left out for amd64 users, or included via a
> use flag. reiser4 isn't yet stable or proven on amd64.
Honestly no matter what your opinion of resier4 is, this patch needs to
really be added. I see that amd64 has mm-sources in portage, which is a
kernel from kernel.org, and it has ~amd64 KEYWORDS. The argument that
we have always had was that reiser4 was not included in a kernel.org
kernel. This is no longer true. Now, I can understand not *supporting*
it until it hits vanilla, but we shouldn't deny adding patches that
resolve issues with the FS or packages that interact with the FS just
because we dislike it or don't deem the FS stable. I'd say to add the
patch to grub, and if a user hoses up their system, well... they're
knowingly running a very experimental kernel and an arguable file
system.... they can pick up the pieces themselves.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2011-10-31 3:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 18:10 [gentoo-dev] grub reiser4 Chris Bainbridge
2005-09-29 18:32 ` Mike Frysinger
2005-10-03 3:57 ` Mike Doty
2005-10-03 9:10 ` Chris Bainbridge
2005-10-03 12:47 ` Luis Medinas
2005-10-03 13:17 ` Chris Gianelloni
2005-10-05 11:13 ` Roy Marples
2005-10-03 13:09 ` Chris Gianelloni [this message]
2005-09-29 18:38 ` Bjarke Istrup Pedersen
2005-10-02 3:50 ` [gentoo-dev] " R Hill
2005-10-02 10:02 ` Chris Bainbridge
2005-10-02 16:04 ` Alec Warner
2005-10-02 16:38 ` Chris Bainbridge
2005-10-02 17:19 ` Dan Meltzer
2005-10-02 17:43 ` Chris Bainbridge
2005-10-02 23:51 ` [gentoo-dev] " Duncan
2005-10-03 12:57 ` [gentoo-dev] " Chris Gianelloni
2005-10-03 12:54 ` Chris Gianelloni
2005-10-03 13:43 ` [gentoo-dev] " Duncan
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=1128344949.6692.22.camel@cgianelloni.nuvox.net \
--to=wolf31o2@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