From: justin <jlec@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] openrc portage news item
Date: Thu, 14 Apr 2011 10:19:50 +0200 [thread overview]
Message-ID: <4DA6AE26.6060009@gentoo.org> (raw)
In-Reply-To: <BANLkTimNdzUK9SvWWYa4Zaa_JCKpinpa+A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On 14/04/11 09:21, Dirkjan Ochtman wrote:
> On Thu, Apr 14, 2011 at 07:30, justin <jlec@gentoo.org> wrote:
>> To me, it doesn't makes it totally clear that you screw everything when
>> rebooting before following the guide. Perhaps this should be made much
>> clearer.
>
> Huh?
>
> "After you install these packages, please do not reboot your system
> until you follow the upgrade guide located at
> http://www.gentoo.org/doc/en/openrc-migration.xml.
>
> It is important that you follow the guide as soon as possible after
> these packages are upgraded. Otherwise, there is a chance that your
> system will not reboot properly."
>
> Seem quite clear to me.
>
> Cheers,
>
> Dirkjan
_Underline_ or write it capital, I don't know. For us and those who know
gentoo this is clear. But user tend to over read things. I would do a
bet that a number of people will cry, because they just rebooted,
because they stopped reading till there; beside those who do not even
read the news item.
So really would suggest doing ugly things like *ATTENTION* or so.
justin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-04-14 8:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 18:15 [gentoo-dev] openrc portage news item William Hubbs
2011-04-13 18:27 ` Thomas Beierlein
2011-04-13 18:32 ` justin
2011-04-13 18:41 ` "Paweł Hajdan, Jr."
2011-04-13 19:58 ` William Hubbs
2011-04-14 8:09 ` [gentoo-dev] " Duncan
2011-04-14 11:44 ` Rich Freeman
2011-04-15 14:04 ` Peter Hjalmarsson
2011-04-15 19:01 ` Duncan
2011-04-13 19:56 ` [gentoo-dev] " William Hubbs
2011-04-14 5:30 ` justin
2011-04-14 7:21 ` Dirkjan Ochtman
2011-04-14 8:19 ` justin [this message]
2011-04-14 8:40 ` [gentoo-dev] " Duncan
2011-04-14 14:44 ` Dale
2011-04-14 15:41 ` Matthew Summers
2011-04-14 16:12 ` Dale
2011-04-14 18:48 ` William Hubbs
2011-04-14 10:32 ` [gentoo-dev] " Kfir Lavi
2011-04-14 10:32 ` Kfir Lavi
2011-04-14 10:51 ` Tomá? Chvátal
2011-04-14 11:03 ` Pacho Ramos
2011-04-14 11:21 ` Thomas Beierlein
2011-04-14 11:27 ` Sylvain Alain
2011-04-21 1:12 ` Donnie Berkholz
2011-04-21 2:23 ` Jeroen Roovers
2011-04-21 2:34 ` Jeroen Roovers
2011-04-22 10:39 ` Lars Wendler
2011-04-29 18:41 ` Brian Harring
2011-04-30 2:19 ` William Hubbs
2011-04-30 4:59 ` Brian Harring
2011-04-30 7:13 ` [gentoo-dev] " Duncan
2011-04-30 11:46 ` Brian Harring
2011-04-30 12:03 ` Rich Freeman
2011-04-30 12:58 ` Brian Harring
2011-04-30 13:06 ` Jeremy Olexa
2011-04-30 13:40 ` Brian Harring
2011-04-29 7:08 ` [gentoo-dev] " William Hubbs
2011-04-29 11:21 ` Rich Freeman
2011-04-29 11:28 ` Ciaran McCreesh
2011-04-29 17:18 ` Alex Alexander
2011-04-29 17:25 ` Ulrich Mueller
2011-04-29 17:32 ` Alex Alexander
2011-04-29 17:52 ` Rich Freeman
2011-04-29 17:58 ` Alex Alexander
2011-04-30 0:34 ` William Hubbs
2011-04-30 9:04 ` Sergei Trofimovich
2011-04-30 12:41 ` Roy Bamford
2011-04-29 14:27 ` [gentoo-dev] " Duncan
2011-05-01 19:12 ` [gentoo-dev] " William Hubbs
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=4DA6AE26.6060009@gentoo.org \
--to=jlec@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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