From: Bas Mevissen <ml@basmevissen.nl>
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: Dominik Brodowski <linux@brodo.de>, cpufreq@www.linux.org.uk
Subject: Re: cpufreq and 2.4.
Date: Mon, 18 Aug 2003 15:21:31 +0200 [thread overview]
Message-ID: <3F40D2DB.30307@basmevissen.nl> (raw)
In-Reply-To: <20030818124944.GE18032@poupinou.org>
Ducrot Bruno wrote:
>
> You mean you can translate french documentations to english, correct?
> Anyway, I would probably have something at my site but only in French
> scheduled for the next week in order to get C) (can not be more fast
> at that time, sorry), and start an English version if nobody
> can not help me to translate.
>
Well, I think your English is good enough to translate what you have
from French to English.
My idea is to define what we want to have documented and then see what
is there and what needs to be written and split that up somehow.
>>I think it to be a good way to learn about cpufreq internals by writing
>>documentation for it.
> Unfortunately, I will do only C) which is the _user_ point-of-view of
> cpufreq.
>
Yes, but even from a user point of view you want to know what happens. I
have no intention to write full documentation. But just a good
description of what happens and how to let it happen.
Regards,
Bas.
next prev parent reply other threads:[~2003-08-18 13:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 15:35 cpufreq and 2.4 Dominik Brodowski
2003-08-18 7:39 ` Ducrot Bruno
2003-08-18 10:14 ` Bas Mevissen
2003-08-18 12:49 ` Ducrot Bruno
2003-08-18 13:21 ` Bas Mevissen [this message]
2003-08-18 10:47 ` Bas Mevissen
2003-08-18 10:57 ` Russell King
2003-08-18 12:13 ` Bas Mevissen
2003-08-18 18:10 ` Russell King
2003-08-18 18:00 ` Dominik Brodowski
2003-08-19 7:24 ` Ducrot Bruno
2003-08-19 8:58 ` Bas Mevissen
2003-08-19 8:45 ` Bas Mevissen
2003-08-19 11:42 ` Ducrot Bruno
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=3F40D2DB.30307@basmevissen.nl \
--to=ml@basmevissen.nl \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.org \
--cc=linux@brodo.de \
/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