From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Getting Important Updates To Users
Date: Mon, 31 Oct 2005 15:19:50 -0600 [thread overview]
Message-ID: <20051031211949.GA8373@nightcrawler> (raw)
In-Reply-To: <82e554630510311256q6af11c0asac769c68b96d4871@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
On Mon, Oct 31, 2005 at 03:56:08PM -0500, Dave Shanker wrote:
> What about Portage auto generating a upgrade file
> (/usr/portage/notices (like it does with it's cache) and then
> providing a notice at the end of an emerge than lets the user know
> it's there and how to read it. We could even provide a switch in
> portage to read the file and display the notices (emerge
> --readnotice).
I suggest y'all work out how you're going to push news, news items,
how it's going to be filterable for those who don't want to see php,
etc, rather then talking about emerge doing differing things...
emerge --news sounds nice and fluffy without getting into the
questions above, where it's going to be shoved into the tree (how it's
going to work for remote trees), etc.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-31 21:23 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 7:42 [gentoo-dev] Getting Important Updates To Users Chris White
2005-10-30 9:06 ` Wernfried Haas
2005-10-30 16:54 ` Michiel de Bruijne
2005-10-30 17:18 ` Qian Qiao
2005-10-30 23:44 ` Dale
2005-10-31 14:16 ` Chris Gianelloni
2005-10-30 15:52 ` Thierry Carrez
2005-10-30 19:03 ` Donnie Berkholz
2005-10-30 20:51 ` [gentoo-dev] " Duncan
2005-10-30 21:59 ` Donnie Berkholz
2005-10-31 1:42 ` [gentoo-dev] " Stuart Herbert
2005-10-31 4:24 ` Chris White
2005-10-31 9:18 ` Stuart Herbert
2005-10-31 14:22 ` Chris Gianelloni
2005-10-31 14:40 ` Lance Albertson
2005-10-31 16:50 ` Stuart Herbert
2005-10-31 17:11 ` Simon Stelling
2005-10-31 18:55 ` Xavier Neys
2005-10-31 19:03 ` Ciaran McCreesh
2005-10-31 19:14 ` Chris Gianelloni
2005-10-31 19:08 ` Stuart Herbert
2005-11-01 0:32 ` [gentoo-dev] " Duncan
2005-11-04 14:25 ` Xavier Neys
2005-11-10 20:14 ` Stuart Herbert
2005-10-31 18:56 ` [gentoo-dev] " Stuart Herbert
2005-10-31 19:06 ` Mike Doty
2005-10-31 19:07 ` Ciaran McCreesh
2005-10-31 19:15 ` Stuart Herbert
2005-11-01 0:52 ` [gentoo-dev] " Duncan
2005-10-31 17:17 ` [gentoo-dev] " Lance Albertson
2005-10-31 19:05 ` Stuart Herbert
2005-10-31 20:07 ` David Morgan
2005-10-31 20:56 ` Dave Shanker
2005-10-31 21:07 ` Frido Ferdinand
2005-10-31 21:19 ` Brian Harring [this message]
2005-10-31 20:58 ` Bruno
2005-11-01 1:20 ` [gentoo-dev] " Duncan
2005-11-03 13:42 ` Nathan L. Adams
2005-10-31 23:20 ` [gentoo-dev] " Corey Shields
2005-11-01 1:05 ` Nathan L. Adams
2005-10-31 9:51 ` Sven Vermeulen
2005-10-31 10:55 ` Xavier Neys
2005-11-01 0:08 ` [gentoo-dev] " Duncan
2005-11-04 1:55 ` [gentoo-dev] " Daniel Drake
2005-10-31 14:12 ` Chris Gianelloni
2005-10-31 14:38 ` Lance Albertson
2005-11-01 3:11 ` pclouds
2005-11-01 3:21 ` Ciaran McCreesh
2005-11-01 14:29 ` Chris Gianelloni
2005-11-02 11:15 ` Paul de Vrieze
2005-11-02 22:11 ` lnxg33k
2005-11-01 14:27 ` Chris Gianelloni
2005-11-03 13:34 ` Nathan L. Adams
2005-11-04 14:11 ` Sven Vermeulen
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=20051031211949.GA8373@nightcrawler \
--to=ferringb@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