From: Marius Mauch <genone@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Bugzilla "Feature" Bugs
Date: Wed, 7 Jan 2004 17:28:38 +0100 [thread overview]
Message-ID: <20040107172838.2671f1dc@sven.genone.homeip.net> (raw)
In-Reply-To: <200401072241.31391.jasonbstubbs@mailandnews.com>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
On 01/07/04 Jason Stubbs wrote:
> 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?
Actually there already is a bug for that, check for "portage 3".
Although it is not really used lately.
Marius
--
Public Key at http://www.genone.de/info/gpg-key.pub
In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-07 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 13:41 [gentoo-portage-dev] Bugzilla "Feature" Bugs Jason Stubbs
2004-01-07 16:28 ` Marius Mauch [this message]
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=20040107172838.2671f1dc@sven.genone.homeip.net \
--to=genone@gentoo.org \
--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