public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [PATCHES] kernel-2.eclass: Various changes requested by users. + [STABLEREQ?] sys-kernel/gentoo-sources-3.8.7: Any objections against stabilizing?
Date: Sun, 14 Apr 2013 12:06:48 +0200	[thread overview]
Message-ID: <1365934008.6940.12.camel@localhost> (raw)
In-Reply-To: <20130414040854.7f672faa@caribou.gateway.2wire.net>

El dom, 14-04-2013 a las 04:08 -0600, Ryan Hill escribió:
> On Sun, 14 Apr 2013 10:23:00 +0200
> "Andreas K. Huettel" <dilfridge@gentoo.org> wrote:
> 
> > Am Sonntag, 14. April 2013, 10:24:18 schrieb Ryan Hill:
> > >
> > > Personally I think that the entire idea of only displaying messages on the
> > > first install is completely asinine.  What exactly is the benefit?  Were
> > > users complaining that we were being too helpful and they'd like us to
> > > hide important messages in random places?
> > 
> > No. They are just not reading it when the only new and relevant message is 
> > drowned in repetitive spam.
> 
> So the solution is to not display them at all?  New messages won't be printed
> unless the maintainer uses REPLACING_VERSIONS, in which case you get exactly
> the same behaviour as now, ie. "drowned in repetitive spam".  All this does is
> reduce the chance of the user ever seeing important information.  If they
> happen to miss it the first time they're SOL.  Are cosmetics really a bigger
> concern than keeping users informed?
> 
> 

The messages are shown the first time by elog *and* saved
in /usr/share/doc/*/README.gentoo, adding the advantage of users having
that docs always present without needing to re-emerge the package or
manually read ebuilds



  reply	other threads:[~2013-04-14 10:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 21:41 [gentoo-dev] [PATCHES] kernel-2.eclass: Various changes requested by users. + [STABLEREQ?] sys-kernel/gentoo-sources-3.8.7: Any objections against stabilizing? Tom Wijsman
2013-04-13  7:03 ` Fabio Erculiani
2013-04-13  9:07   ` Tom Wijsman
2013-04-14  5:09 ` [gentoo-dev] " Ryan Hill
2013-04-14  6:55   ` Tom Wijsman
2013-04-14  8:24     ` Ryan Hill
2013-04-14  8:23       ` Andreas K. Huettel
2013-04-14 10:08         ` Ryan Hill
2013-04-14 10:06           ` Pacho Ramos [this message]
2013-04-14 10:52             ` Tom Wijsman
2013-04-14 15:02               ` Alan McKinnon
2013-04-14 17:15             ` Andreas K. Huettel
2013-04-14 17:21               ` Pacho Ramos
2013-04-14  9:31       ` Pacho Ramos
2013-04-14  9:29     ` Pacho Ramos

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=1365934008.6940.12.camel@localhost \
    --to=pacho@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