public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Martin Dalecki <dalecki@evision-ventures.com>,
	linux-kernel@vger.kernel.org
Subject: Re: kb25 manual [was Re: [Linux-usb-users] Re: What to do with all of the USB UHCI drivers in the kernel?]
Date: Thu, 23 May 2002 18:01:36 +0200	[thread overview]
Message-ID: <20020523160136.GC24260@louise.pinerecords.com> (raw)
In-Reply-To: <20020523154252.GA24260@louise.pinerecords.com> <Pine.LNX.4.33L2.0205230850080.4119-100000@dragon.pdx.osdl.net>

> | > BTW> one of the reasons I never bothered myself with kbuild-2.5
> | > is for example that nio matter how frequently Keith
> | > is advertising it - every time I go there to have a look at it
> | > at sf what I find is a scatter heap of .tar.gz. The documentation
> | > about how to install it makes me nervous, since I would
> | > rather just expect a diff and a README how to use it, so I never
> | > look after it.
> |
> | Duh... All you need is the core package (diff #1), the architecture
> | independent modifications package (diff #2) and finally diff #3 that
> | adds the arch-specific stuff. Everything's in a single list on sf.
> |
> | then just do s/t like
> | cd /usr/src/linux-2.4.19-pre8 && zcat \
> | 	../kbuild-2.5-core-14.gz \
> | 	../kbuild-2.5-common-2.4.19-pre8-1.gz \
> | 	../kbuild-2.5-i386-2.4.19-pre8-1.gz \
> | 	| patch -sp1
> |
> | and read the comprehensive manual in Documentation/kbuild/
> |
> | What's there to be nervous about?
> 
> so there should just be a short, simple readme about how to
> install and use it -- not one that is 2400 lines long.
> Other than that, I like it.

How about submitting one to Keith yourself then? :)

No really, I don't think there's a problem with the manual.
If you just want to learn how to compile a kernel, you can
skim thru the first section of the file in under 30 seconds.

> Other than that, I like it.

Who doesn't. I mean, apart from Wayne Brown who hates to have
to remember to issue simpler commands. ;)


T.

  reply	other threads:[~2002-05-23 16:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-20 22:31 What to do with all of the USB UHCI drivers in the kernel? Greg KH
2002-05-21 15:23 ` [Linux-usb-users] " Timothy E. Jedlicka - wrk
2002-05-21 20:10   ` Greg KH
2002-05-22  1:10 ` André Bonin
2002-05-22 19:21   ` Greg KH
2002-05-22 19:35     ` Andre Bonin
2002-05-22 20:15       ` Greg KH
2002-05-23  6:34         ` Martin Dalecki
2002-05-23 14:48           ` [Linux-usb-users] " Stephen J. Gowdy
2002-05-23 14:25             ` Martin Dalecki
2002-05-23 15:11               ` [Linux-usb-users] Re: What to do with all of the USB UHCI driversin " Gunther Mayer
2002-05-23 15:42               ` kb25 manual [was Re: [Linux-usb-users] Re: What to do with all of the USB UHCI drivers in the kernel?] Tomas Szepe
2002-05-23 15:51                 ` Randy.Dunlap
2002-05-23 16:01                   ` Tomas Szepe [this message]
2002-05-23 17:46                     ` Martin Dalecki
2002-05-23 19:09                       ` Tomas Szepe
2002-05-23 16:04               ` [Linux-usb-users] Re: What to do with all of the USB UHCI drivers in the kernel? Greg KH
2002-05-23 17:55                 ` Martin Dalecki
2002-05-24  8:21                   ` [Linux-usb-users] Re: What to do with all of the USB UHCI drivers Peter Wächtler
2002-05-24 14:07                     ` Gunther Mayer
2002-05-24 15:13                       ` Stephen J. Gowdy
2002-05-23 15:16           ` [linux-usb-devel] Re: What to do with all of the USB UHCI drivers in the kernel? David Brownell
2002-05-23 17:41 ` Peter Osterlund
2002-05-23 17:48   ` Greg KH
2002-05-23 18:16 ` Peter Osterlund
2002-05-23 19:24 ` Pierre Rousselet

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=20020523160136.GC24260@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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