From: Bart Samwel <bart@samwel.tk>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 10/14/] Doc. sources: expose laptop-mode
Date: Tue, 23 May 2006 10:37:36 +0200 [thread overview]
Message-ID: <4472C9D0.9010508@samwel.tk> (raw)
In-Reply-To: <20060522083531.ad725cdf.rdunlap@xenotime.net>
Randy.Dunlap wrote:
> On Mon, 22 May 2006 07:23:13 +0200 Bart Samwel wrote:
>> Point for discussion: should the laptop_mode script really still be in
>> laptop-mode.txt? AFAIK most distros use laptop-mode-tools or use their
>> own scripts to control this. Furthermore, the existing script is mostly
>> unmaintained, and it is full of bugs that were fixed long ago in
>> laptop-mode-tools (which was originally a fork of the script). I think
>> it would be better to replace it with a bit of documentation on which
>> things a laptop mode control script *should* tweak, *may want to* tweak,
>> etc., accompanied by an explanation why these tweaks are needed. I.e, an
>> "annotated spec", as one would expect to find in documentation. I'll
>> submit a patch to this effect when I find some time.
>
> If it's really so unmaintained and mostly replaced, sounds like it should
> be removed. OTOH, if you want to keep several source files and/or
> scripts, I would prefer to see a laptop-mode subdirectory for them.
I'm all for completely removing the script, so no subdirectories needed
as far as I'm concerned. I'll submit a patch to replace the script by
some text explaining what such a script should do.
Cheers,
Bart
next prev parent reply other threads:[~2006-05-23 8:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060521203349.40b40930.rdunlap@xenotime.net>
2006-05-22 3:57 ` [PATCH 2/14/] Doc. sources: expose vm/ Randy.Dunlap
2006-05-22 3:57 ` [PATCH 3/14/] Doc. sources: expose video4linux/ Randy.Dunlap
2006-05-22 3:57 ` [PATCH 4/14/] Doc. sources: expose block/ Randy.Dunlap
2006-05-22 3:57 ` [PATCH 5/14/] Doc. sources: expose s390/ Randy.Dunlap
2006-05-22 3:57 ` [PATCH 6/14/] Doc. sources: expose pcmcia/ Randy.Dunlap
2006-05-29 15:17 ` Dominik Brodowski
2006-05-22 3:57 ` [PATCH 7/14/] Doc. sources: expose rtc Randy.Dunlap
2006-05-22 3:57 ` [PATCH 8/14/] Doc. sources: expose smount Randy.Dunlap
2006-05-22 3:57 ` [PATCH 9/14/] Doc. sources: expose dnotify Randy.Dunlap
2006-05-22 3:57 ` [PATCH 10/14/] Doc. sources: expose laptop-mode Randy.Dunlap
2006-05-22 5:23 ` Bart Samwel
2006-05-22 15:35 ` Randy.Dunlap
2006-05-23 8:37 ` Bart Samwel [this message]
2006-05-22 3:57 ` [PATCH 11/14/] Doc. sources: expose hpet Randy.Dunlap
2006-05-22 3:57 ` [PATCH 12/14/] Doc. sources: expose java Randy.Dunlap
2006-05-22 3:57 ` [PATCH 13/14/] Doc. sources: expose mtrr Randy.Dunlap
2006-05-22 3:57 ` [PATCH 14/14/] Doc. sources: expose kprobes Randy.Dunlap
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=4472C9D0.9010508@samwel.tk \
--to=bart@samwel.tk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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