From: Jared Lindsay <cinder.sub@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Best Desktop Patchset for kernel
Date: Wed, 5 Oct 2005 14:54:38 -0700 [thread overview]
Message-ID: <e16d914c0510051454w33e6c194i691811cf5a77168@mail.gmail.com> (raw)
In-Reply-To: <200510051926.49092.volker.armin.hemmann@tu-clausthal.de>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
Yep, nitro is "only" ck + bootsplash + some other stuff. And guess what?
That's why I use it, and not ck! I have never had any problems with it, and
I find it to be a better patchset than gentoo-sources. I only wish it was
updated more often, but the maintainer is pretty busy right now.
And I don't care a whole lot that nitro is unsupported. The dev I asked on
the issue simply said they don't want to have to provide support for tons of
kernel patchsets, which I agree they shouldn't have to do. I have also found
that a lot of naysayers haven't even used nitro, or only used a much older
version, which makes me skeptical.
On 10/5/05, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de>
wrote:
>
> Hi,
>
> ok, coaranm aside - have you EVER seen a dev recommending love- or
> nitro-sources?
>
> I have not! Never! Never ever!
>
> There seems to be a reason that a) no dev has recommended them so far and
> b)
> they are not in portage.
>
> And puulease.. nitro is nothing more than
> ck+bootsplash+someotherunneededstuff.
>
> If you want the 'latency enhancement' of nitro, go directly to ck - Con
> Kolivas knows what he does.
> --
> gentoo-amd64@gentoo.org mailing list
>
>
[-- Attachment #2: Type: text/html, Size: 1624 bytes --]
next prev parent reply other threads:[~2005-10-05 21:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 0:37 [gentoo-amd64] Best Desktop Patchset for kernel Karol Krizka
2005-10-05 1:04 ` Hemmann, Volker Armin
2005-10-05 1:04 ` Mark Knecht
2005-10-05 1:37 ` Jared Lindsay
2005-10-05 2:35 ` Hemmann, Volker Armin
2005-10-05 2:40 ` Mark Knecht
2005-10-05 3:40 ` Jared Lindsay
2005-10-05 3:50 ` Taka John Brunkhorst
2005-10-05 4:28 ` Hemmann, Volker Armin
2005-10-05 13:42 ` [gentoo-amd64] " Duncan
2005-10-05 17:26 ` Hemmann, Volker Armin
2005-10-05 18:01 ` Olivier Crete
2005-10-05 20:24 ` Hemmann, Volker Armin
2005-10-05 18:24 ` [gentoo-amd64] " Duncan
2005-10-05 21:54 ` Jared Lindsay [this message]
2005-10-06 5:19 ` Duncan
2005-10-06 6:53 ` Hemmann, Volker Armin
2005-10-06 15:59 ` [gentoo-amd64] " Duncan
2005-10-06 16:35 ` Marco Matthies
2005-10-06 21:27 ` [gentoo-amd64] " Duncan
2005-10-06 20:59 ` [gentoo-amd64] " Jared Lindsay
2005-10-06 21:42 ` [gentoo-amd64] " Duncan
2005-10-06 21:47 ` [gentoo-amd64] " Tres Melton
2005-10-11 22:12 ` [gentoo-amd64] " Billy Holmes
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=e16d914c0510051454w33e6c194i691811cf5a77168@mail.gmail.com \
--to=cinder.sub@gmail.com \
--cc=gentoo-amd64@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