From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add tlp.
Date: Fri, 10 Feb 2017 16:38:01 +0100 [thread overview]
Message-ID: <8737fmcazq.fsf@gnu.org> (raw)
In-Reply-To: <20170210141414.GA22019@jocasta.intra> (John Darrington's message of "Fri, 10 Feb 2017 15:14:14 +0100")
John Darrington <john@darrington.wattle.id.au> skribis:
> On Fri, Feb 10, 2017 at 01:49:07PM +0100, Ludovic Court??s wrote:
> John Darrington <john@darrington.wattle.id.au> skribis:
>
> > On Tue, Jan 31, 2017 at 10:01:18PM +0100, Mathieu Othacehe wrote:
> >
> > + (home-page "http://linrunner.de/en/tlp/tlp.html")
> > + (synopsis "Power management tool for Linux")
> > + (description "TLP is a power management tool for Linux. It comes with
> >
> > Shouldn't we changed "Linux" to "Linux based GNU systems" or something similar?
>
> It uses interfaces specific to the kernel Linux so I think it???s
> technically correct.
>
> But grammatically incorrect. Specifically, the preposition "for" is wrong.
> It implies that the package provides some feature that Linux can use. Whereas
> the opposite is true.
>
> A more gramatically correct sentance might say "power management tool using
> Linux kernel features".
Right, or “for Linux-based operating systems.”
I’m happy if you make one of these changes. :-)
> But I wonder why we even mention it? I mean if a package happens to use libc, we don't
> say in the package description or sysnopsis "an editor which makes using the
> fopen, and fclose calls of glibc".
I think we mention it because while GuixSD uses glibc, it may be able to
use different kernels in the future.
Ludo’.
prev parent reply other threads:[~2017-02-10 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 21:01 [PATCH] gnu: Add tlp Mathieu Othacehe
2017-02-09 22:27 ` Ludovic Courtès
2017-02-10 6:26 ` John Darrington
2017-02-10 12:49 ` Ludovic Courtès
2017-02-10 14:14 ` John Darrington
2017-02-10 14:30 ` David Craven
2017-02-10 15:38 ` Ludovic Courtès [this message]
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=8737fmcazq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.