From: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: using bug reports on vendor kernels
Date: Thu, 9 Aug 2001 23:42:38 +0200 [thread overview]
Message-ID: <01080923423801.04822@idun> (raw)
In-Reply-To: <200108092131.f79LV4Hr024656@webber.adilger.int>
In-Reply-To: <200108092131.f79LV4Hr024656@webber.adilger.int>
Am Donnerstag, 9. August 2001 23:31 schrieben Sie:
> Oliver writes:
> > is there a site that would allow me to browse a list of patches added to
> > vendor kernels (esp. RedHat). I need this to use an oops supplied by a
> > user.
>
> You _should_ be able to simply get the RedHat source RPM, and have a look
> at the various patches that are applied to the base Linus kernel. At least
> that is how the Turbolinux and SuSE kernels are built (haven't looked
> at a RedHat kernel in a while, but I expect the same). Granted, some
> of the patch names are not exactly self explanitory (e.g. jumbo patches
> like -ac or -aa, which have their own documentation somewhere, often l-k).
It might do so. However the speed of my internet connectivity would make this
a very, very slow task.
And the day after having completed that I'd be bound to get a bug report from
a Mandrake user.
Regards
Oliver
next prev parent reply other threads:[~2001-08-09 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 21:02 Oliver Neukum
2001-08-09 21:15 ` arjan
2001-08-09 21:34 ` Bill Rugolsky Jr.
2001-08-09 21:46 ` Arjan van de Ven
2001-08-09 21:55 ` Bill Rugolsky Jr.
2001-08-10 8:24 ` Ville Herva
2001-08-09 21:31 ` Andreas Dilger
2001-08-09 21:42 ` Oliver Neukum [this message]
2001-08-09 21:59 ` Bill Rugolsky Jr.
2001-08-10 9:42 ` Chmouel Boudjnah
2001-08-10 1:32 ` Ignacio Vazquez-Abrams
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=01080923423801.04822@idun \
--to=oliver.neukum@lrz.uni-muenchen.de \
--cc=adilger@turbolinux.com \
--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
all inboxes | Powered by JetHome®