From: devzero@web.de
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: distro specific kernels vs vanilla kernel and how to compare among each other
Date: Sat, 17 Nov 2007 13:32:28 +0100 [thread overview]
Message-ID: <2090880485@web.de> (raw)
besides a web-browseable directory structure with all the single broken-out patches (which are typically part of src.rpm or similar) , i assume it would be good to put those patched and unpatched kernel sources online via lxr ? ( http://lxr.linux.no/ )
> -----Ursprüngliche Nachricht-----
> Von: "Andi Kleen" <andi@firstfloor.org>
> Gesendet: 16.11.07 23:25:29
> An: devzero@web.de
> CC: linux-kernel@vger.kernel.org
> Betreff: Re: distro specific kernels vs vanilla kernel and how to compare among each other
>
> devzero@web.de writes:
>
> > does somebody know if there is a website or a project for giving comfortable and deeper insight into what`s specific to distro`s kernels and what`s their difference to vanilla kernel ?
> >
> > i mean some way to have some transparancy to what different distro vendors add to vanilla kernel sources and thus turning it into their own specific version.
>
> There used to be such a page at kernelnewbies, but at some point it disappeared.
>
> I agree it would be a useful resource.
>
> -Andi
>
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
next reply other threads:[~2007-11-17 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 12:32 devzero [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-16 19:45 distro specific kernels vs vanilla kernel and how to compare among each other devzero
2007-11-16 22:25 ` Andi Kleen
2007-11-17 5:17 ` ewanm89
2007-11-19 12:55 ` Christoph Hellwig
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=2090880485@web.de \
--to=devzero@web.de \
--cc=andi@firstfloor.org \
--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