From: Lee Revell <rlrevell@joe-job.com>
To: Dave Airlie <airlied@linux.ie>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: running Linus kernel on FC3
Date: Wed, 29 Dec 2004 04:48:21 -0500 [thread overview]
Message-ID: <1104313701.2984.11.camel@krustophenia.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0412290922420.2899@skynet>
On Wed, 2004-12-29 at 09:25 +0000, Dave Airlie wrote:
> Well I thought people might be seeing the same things... it's just Linus
> kernel with FC3 config....
>
> RH have said before that they try to keep their Fedora kernels as close to
> Linus as possible, just wondering is this one area they've gone their own
> way..
Just install the kernel source RPM and look at the patches.
But, this is a bit OT for LKML, try the Fedora lists.
Lee
next prev parent reply other threads:[~2004-12-29 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 8:57 running Linus kernel on FC3 Dave Airlie
2004-12-29 9:20 ` Valdis.Kletnieks
2004-12-29 9:25 ` Dave Airlie
2004-12-29 9:48 ` Lee Revell [this message]
2004-12-29 9:48 ` Valdis.Kletnieks
2004-12-29 19:57 ` Alan Cox
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=1104313701.2984.11.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.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