From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Interactive Portage Development
Date: Tue, 22 Aug 2006 18:55:59 -0400 [thread overview]
Message-ID: <44EB8B7F.3040406@gentoo.org> (raw)
I only see the same 10 or 12 people commenting on gentoo-portage-dev, so
if you are even remotely interested in portage development or interested
in a sane API, or interested in seeing new features I would suggest you
do two things.
One is look on archives.gentoo.org and see what we have been talking about.
Two is subscribe to the list and comment on the proposals there.
No Discussion means no perceived progress. So help us discuss and iron
our stuff that YOU want to see.
-Alec Warner
"I guess I should re-add myself to the Portage Team" Portage Team Member.
--
gentoo-dev@gentoo.org mailing list
reply other threads:[~2006-08-22 22:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44EB8B7F.3040406@gentoo.org \
--to=antarus@gentoo.org \
--cc=gentoo-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