From: Richard Hughes <hughsient@gmail.com>
To: Jordan Crouse <jordan.crouse@amd.com>
Cc: linux-pm@lists.osdl.org
Subject: Re: suspend and hibernate nomenclature
Date: Mon, 08 May 2006 17:09:10 +0100 [thread overview]
Message-ID: <1147104551.4071.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20060508150512.GJ4761@cosmic.amd.com>
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
On Mon, 2006-05-08 at 09:05 -0600, Jordan Crouse wrote:
> On 07/05/06 19:02 +0100, Richard Hughes wrote:
> > First, sorry for the random mail to this mailing list.
> >
> > I'm the developer of gnome-power-manager. The latest mini-project of
> > mine is to fix the suspend-hibernate nomenclature used by OSS projects.
> >
> > This might not effect the lowest layers of the stack (i.e. I want to
> > focus on the stuff used by *users*), so this might not be applicable to
> > you guys.
>
> I would say thats probably a pretty accurate assessment. Since you are a GUI
> developer, you can tell the users whatever you want, and you can translate
> under the scenes. In that case, using terms like "hibernate" makes perfect
> sense.
Sure, agreed.
> But at the lower level, I favor a more clinical terminology, because it
> reduces confusion amongst system developers. Thats not to say that our
> current terminology is sane, (because it isn't), but I would far prefer
> precise numbers over vague synonyms for sleeping. :)
Up to you guys :-)
> *Our* task, as I see it, is to make sure that the underlying descriptions
> are intelligent and persistent, so *you* don't have to change your
> application every time something a new kernel is released. But as soon as
> we've figured that out, then it will be no thing for you to take an
> "hibernate" from the top end, and turn it into the right term for the kernel.
Sure, I totally agree the user shouldn't know about any of this stuff,
but I thought I should bring the website to your attention to keep you
guys in the loop with GUI users... :-)
Anyway, thanks for this mail, feedback has been great so far.
Richard.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-05-08 16:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 18:02 suspend and hibernate nomenclature Richard Hughes
2006-05-08 15:05 ` Jordan Crouse
2006-05-08 16:09 ` Richard Hughes [this message]
2006-05-08 20:01 ` Pavel Machek
2006-05-14 15:32 ` Richard Hughes
2006-05-14 15:39 ` Pavel Machek
2006-05-14 21:17 ` Rafael J. Wysocki
2006-05-08 23:47 ` David Brownell
2006-05-09 7:38 ` Richard Hughes
2006-05-09 15:57 ` David Brownell
2006-05-16 20:40 ` Pavel Machek
2006-05-18 19:56 ` David Brownell
2006-05-18 20:50 ` Pavel Machek
2006-05-19 2:25 ` David Brownell
2006-05-20 17:20 ` Pavel Machek
2006-05-20 19:23 ` Alan Stern
2006-05-20 20:47 ` David Brownell
2006-05-20 20:55 ` Pavel Machek
2006-05-21 15:35 ` Alan Stern
2006-05-20 20:54 ` David Brownell
2006-05-20 22:39 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-05-16 20:47 Scott E. Preece
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=1147104551.4071.6.camel@localhost.localdomain \
--to=hughsient@gmail.com \
--cc=jordan.crouse@amd.com \
--cc=linux-pm@lists.osdl.org \
--cc=richard@hughsie.com \
/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