public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paulo Jorge de Oliveira Cantante de Matos <pocm@netvisao.pt>
To: Gentoo Dev ML <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Ebuilds from bugs -> portage unstable -> portage stable
Date: Tue, 21 Oct 2003 01:48:02 +0000	[thread overview]
Message-ID: <1066648576.2398.13.camel@localhost> (raw)

Hi all,

I'd like to know more about how an ebuild that shows up in
bugs.gentoo.org goes to portage as unstable and then passes to stable.
Which are the requirements of each of these phases?

Best regards,

-- 

Paulo J. Matos : pocm@mega.ist.utl.pt
Instituto Superior Tecnico - Lisbon
Computer and Software Eng. - A.I.
 - > http://mega.ist.utl.pt/~pocm
---
        -> God had a deadline...
                So, he wrote it all in Lisp!


--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-10-21  0:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21  1:48 Paulo Jorge de Oliveira Cantante de Matos [this message]
2003-10-21 12:58 ` [gentoo-dev] Ebuilds from bugs -> portage unstable -> portage stable Chris Gianelloni

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=1066648576.2398.13.camel@localhost \
    --to=pocm@netvisao.pt \
    --cc=gentoo-dev@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