From: John Nilsson <john@milsson.nu>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Proposal: pre-emerge advisories
Date: Wed, 13 Jul 2005 14:29:28 +0200 [thread overview]
Message-ID: <1121257768.19920.13.camel@newkid.milsson.nu> (raw)
In-Reply-To: <200507131949.44087.jstubbs@gentoo.org>
On ons, 2005-07-13 at 19:49 +0900, Jason Stubbs wrote:
> If developers aren't open to the idea of adding the information you seek to the ChangeLog, they aren't
> likely to be open to adding it anywhere.
However, tools can be more or less encouraging.
Regarding the bug# the bug summary can be automaticly pulled in from
bugzilla. Either, after the fact, when reading the ChangeLog or upon
submitting it.
I'm not familiar with the QA tools currently used by dev. Would it be
possible to have theese tools ask the apropritate questions and put them
into the ChangeLog?
On a related issue, it would be great with a portage-bugzilla tool.
emerge --info and other stuff could be handled automaticly. When an
ebuild breaks the tool would be invoked to show filed bugs and their
links and/or submit a new one.
As it is now portage is great tool for distribution, customization,
compilation, installation and dependency tracking, it could be a better
tool with regards to QA and development.
-John
--
gentoo-portage-dev@gentoo.org mailing list
prev parent reply other threads:[~2005-07-13 12:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 7:40 [gentoo-portage-dev] Proposal: pre-emerge advisories Craig Lawson
2005-07-08 9:51 ` Anthony Gorecki
2005-07-08 15:18 ` Robert Larson
2005-07-09 9:28 ` Jason Stubbs
2005-07-09 23:05 ` Drake Wyrm
2005-07-09 23:19 ` felix
2005-07-10 0:21 ` Jason Stubbs
2005-07-13 6:35 ` Craig Lawson
2005-07-13 6:57 ` [gentoo-portage-dev] cvs head Brian D. Harring
2005-07-13 10:47 ` Jason Stubbs
2005-07-13 12:28 ` Alec Warner
2005-07-13 10:49 ` [gentoo-portage-dev] Proposal: pre-emerge advisories Jason Stubbs
2005-07-13 12:29 ` John Nilsson [this message]
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=1121257768.19920.13.camel@newkid.milsson.nu \
--to=john@milsson.nu \
--cc=gentoo-portage-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