From: Jason Stubbs <jasonbstubbs@mailandnews.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Bugzilla "Feature" Bugs
Date: Wed, 7 Jan 2004 22:41:31 +0900 [thread overview]
Message-ID: <200401072241.31391.jasonbstubbs@mailandnews.com> (raw)
Hi all,
I've just been going through some of the unresolved bugs and have found
(especially in the earlier bug #s) that there are many feature requests that
are unresolved. I'm thinking it would be a good idea to create a "master" bug
for portage-ng and then make it depend on all of these unresolved feature
requests. Pros? It would make it easy to confirm that there's nothing missing
from the reqspec and also make it easy to close many (hundreds?) of bugs on
portage-ng's completion. Cons? Massive amount of deps from a single bug.
Thoughts?
--
Regards,
Jason Stubbs
--
gentoo-portage-dev@gentoo.org mailing list
next reply other threads:[~2004-01-07 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 13:41 Jason Stubbs [this message]
2004-01-07 16:28 ` [gentoo-portage-dev] Bugzilla "Feature" Bugs Marius Mauch
2004-01-08 2:07 ` Jason Stubbs
-- strict thread matches above, loose matches on Subject: below --
2004-01-07 13:40 Jason Stubbs
2004-01-07 14:08 ` Jason Stubbs
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=200401072241.31391.jasonbstubbs@mailandnews.com \
--to=jasonbstubbs@mailandnews.com \
--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