public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Stubbs <jasonstubbs@gawab.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Bugzilla "Feature" Bugs
Date: Thu, 8 Jan 2004 11:07:28 +0900	[thread overview]
Message-ID: <200401081107.28773.jasonstubbs@gawab.com> (raw)
In-Reply-To: <20040107172838.2671f1dc@sven.genone.homeip.net>

On Thursday 08 January 2004 01:28, Marius Mauch wrote:
> 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.

Bug #2765 entitled "Portage 3 TODO"? The first comment actually implies that 
it's a Portage 2 TODO, but anyway...

Do you think it's worth reviving this bug? If given the okay, I'll start going 
through outstanding bugs and adding deps to anything that is a feature 
request.

--
Regards,
Jason Stubbs

--
gentoo-portage-dev@gentoo.org mailing list


  reply	other threads:[~2004-01-08  2:09 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
2004-01-08  2:07   ` Jason Stubbs [this message]
  -- 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=200401081107.28773.jasonstubbs@gawab.com \
    --to=jasonstubbs@gawab.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