cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Matthew Wilcox <willy@debian.org>
Cc: davej@codemonkey.org.uk, maks attems <janitor@sternwelten.at>,
	271396@bugs.debian.org, Gavin Sandie <beach@vicecity.co.uk>,
	cpufreq@www.linux.org.uk
Subject: Re: Bug#271396: Kernel help typo
Date: Tue, 14 Sep 2004 16:10:44 +0100	[thread overview]
Message-ID: <20040914151043.GD13788@redhat.com> (raw)
In-Reply-To: <20040914141117.GZ642@parcelfarce.linux.theplanet.co.uk>

On Tue, Sep 14, 2004 at 03:11:17PM +0100, Matthew Wilcox wrote:
 > On Mon, Sep 13, 2004 at 11:10:11PM +0200, maks attems wrote:
 > >  	  Use the CPUFreq governor 'userspace' as default. This allows
 > >  	  you to set the CPU frequency manually or when an userspace 
 > > -	  programm shall be able to set the CPU dynamically without having
 > > +	  programme shall be able to set the CPU dynamically without having
 > >  	  to enable the userspace governor manually.
 > 
 > In British English, "programme" refers to a television
 > schedule, "program" refers to something a computer runs, see:
 > http://www.chambersharrap.co.uk/chambers/chref/chref.py/main?query=programme&title=21st
 > 
 > Americans use "program" for everything, so using programme here is wrong
 > for everyone ;-)

'program' is what I plumped for too, and thats whats currently
in cpufreq-bk.

		Dave

  reply	other threads:[~2004-09-14 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040912233809.GA4739@nermel>
2004-09-13 21:10 ` Bug#271396: Kernel help typo maks attems
2004-09-13 22:48   ` Francesco Poli
2004-09-14 11:57   ` Dave Jones
2004-09-14 14:11   ` Matthew Wilcox
2004-09-14 15:10     ` Dave Jones [this message]
2004-09-15 17:53     ` maks attems

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=20040914151043.GD13788@redhat.com \
    --to=davej@redhat.com \
    --cc=271396@bugs.debian.org \
    --cc=beach@vicecity.co.uk \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=janitor@sternwelten.at \
    --cc=willy@debian.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