From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Changelogs
Date: Wed, 27 Jul 2005 07:40:53 -0400 [thread overview]
Message-ID: <20050727074053.6b5726f8@nomad.datanode.net> (raw)
In-Reply-To: <pan.2005.07.27.04.16.52.411549@cox.net>
On Tue, 26 Jul 2005 21:16:53 -0700
Duncan <1i5t5.duncan@cox.net> wrote:
>
> Maybe what's needed to address #2 is simply to include a separate
> portage changelog file, somewhere within the tree, possibly as its own
> package, or in the profiles root dir, along with the global
> package.mask, and use.desc and use.local.desc files. Portage could
> then add an "emerge portinfo" function, similar to "emerge info", that
> would spit out the "upstream" changelog between what's currently
> installed, and any new version.
or just a dodoc ChangeLog and have it tossed in the same share dir we
toss upstream docs/changelogs/readmes
/me is not weighing in with an opinion on this, mind you, just saying
there might be an even simpler way to include that info
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-27 11:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 2:05 [gentoo-dev] Changelogs Alec Warner
2005-07-27 2:22 ` Georgi Georgiev
2005-07-27 4:16 ` [gentoo-dev] Changelogs Duncan
2005-07-27 11:40 ` Michael Cummings [this message]
2005-07-27 12:13 ` Simon Stelling
2005-07-27 12:38 ` Michael Cummings
2005-07-27 12:52 ` Alin Nastac
2005-07-27 13:19 ` Alec Joseph Warner
2005-07-27 13:38 ` Simon Stelling
2005-07-27 14:00 ` Alec Joseph Warner
2005-07-27 15:37 ` Georgi Georgiev
2005-07-27 14:58 ` Jason Stubbs
2005-07-27 14:50 ` [gentoo-dev] Changelogs Jason Stubbs
2005-07-28 0:02 ` Alec Warner
2005-07-28 13:58 ` Jason Stubbs
2005-07-27 16:59 ` Maurice van der Pot
2005-07-27 18:23 ` Alec Joseph Warner
2005-07-27 18:29 ` Donnie Berkholz
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=20050727074053.6b5726f8@nomad.datanode.net \
--to=mcummings@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