All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Poli <frx@firenze.linux.it>
To: cpufreq@www.linux.org.uk
Subject: Re: Help with Installation
Date: Sat, 3 Apr 2004 17:16:33 +0200	[thread overview]
Message-ID: <20040403171633.610cc960.frx@firenze.linux.it> (raw)
In-Reply-To: <20040403145045.GV19001@poupinou.org>


[-- Attachment #1.1: Type: text/plain, Size: 903 bytes --]

On Sat, 3 Apr 2004 16:50:45 +0200 Bruno Ducrot wrote:

> tar xzvfp cpufreq-...tar.gz
> cd cpufreq
> ./patchin.sh /path/to/kernel/sources
> 
> Do *not* remove the cpufreq directory that was unpacked.

Why did you set up such a strange procedure?
What are the advantages over a simple patch like the old ones found in
http://www.codemonkey.org.uk/projects/cpufreq/   ?

I'd say a gzipped (or bzip2ed) patch file would be much more easy to
apply (especially with automatic tools such as Debian kernel-package,
that is, make-kpkg), but of course I may be wrong...

Could you please explain the rationale behind such a choice?

-- 
             |  GnuPG Key ID = DD6DFCF4 | You're compiling a program
  Francesco  |        Key fingerprint = | and, all of a sudden, boom!
     Poli    | C979 F34B 27CE 5CD8 DC12 |         -- from APT HOWTO,
             | 31B5 78F4 279B DD6D FCF4 |             version 1.8.0

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq

  reply	other threads:[~2004-04-03 15:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-03 13:42 Help with Installation Ozeki San
2004-04-03 14:50 ` Bruno Ducrot
2004-04-03 15:16   ` Francesco Poli [this message]
2004-04-03 16:22     ` Russell King
2004-04-04 17:57       ` Francesco Poli
2004-04-04 21:11         ` Dominik Brodowski
2004-04-05 20:20           ` Francesco Poli
2004-04-05 21:06             ` Russell King
2004-04-06 21:01               ` Francesco Poli
2004-04-07  7:11                 ` Russell King
2004-04-07 20:26                   ` Francesco Poli
2004-04-05 21:11             ` Dominik Brodowski
2004-04-06  8:25               ` Bruno Ducrot
2004-04-06  8:47                 ` Bruno Ducrot
2004-04-06 21:50                   ` Francesco Poli
2004-04-07 16:18                     ` Bruno Ducrot
2004-04-06 21:48               ` Francesco Poli
2004-04-06 22:00                 ` Dominik Brodowski

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=20040403171633.610cc960.frx@firenze.linux.it \
    --to=frx@firenze.linux.it \
    --cc=cpufreq@www.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.