public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: AllenJB <gentoo-lists@allenjb.me.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Please use "eselect news" items!
Date: Thu, 25 Jun 2009 22:57:08 +0100	[thread overview]
Message-ID: <4A43F2B4.5060100@allenjb.me.uk> (raw)

Hi all,

As a user, I'd like to encourage developers to make use of news items 
(eselect news) for important changes. I find them much more noticeable 
than elog messages (which, while I have set them up so they get emailed 
to me, I admit I don't always read). I think they're also easier to go 
back and re-read later (not everyone knows how to dig out old elog 
messages).

2 recent changes I would suggest having news items for are the libpcre 
.la files issue, because it often doesn't get noticed until later when 
builds fail, and the masking of the "kdeprefix" use flag as this is a 
fairly major change and I think it's useful for users to know why these 
changes are being made.

Another case is that prior to it's masking, the "kdeprefix" use flag was 
deprecated, with only an elog message on every kde package to notify 
users, resulting in users who have their elog messages emailed to them 
receiving a very large number of emails all with the same content - I 
would also suggest news items in such cases in future.


Thanks to all the developers who worked to bring us this long awaited 
feature - I think it's brilliant, so please use it!

AllenJB



             reply	other threads:[~2009-06-25 21:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 21:57 AllenJB [this message]
2009-06-26 12:20 ` [gentoo-dev] Please use "eselect news" items! Ben de Groot
2009-06-26 18:25 ` Fabian Groffen
2009-06-26 19:27   ` Zac Medico
2009-06-26 23:06   ` Alec Warner
2009-06-27  4:43 ` Dale
2009-06-27  6:29   ` Ulrich Mueller
2009-06-27  9:17     ` Dale

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=4A43F2B4.5060100@allenjb.me.uk \
    --to=gentoo-lists@allenjb.me.uk \
    --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