From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 19: Gentoo Stable Portage Tree -- ideas
Date: Thu, 5 Jan 2006 21:35:56 -0800 [thread overview]
Message-ID: <20060106053556.GD28075@nightcrawler.e-centre.net> (raw)
In-Reply-To: <43BDF53C.8080205@leetworks.com>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
On Thu, Jan 05, 2006 at 11:42:36PM -0500, Andrew Muraco wrote:
> Anyways, I would personally like to see if this can stir some interest.
> I would be willing to help test and help make this GLEP a reality,
> however I can not implement this myself as I lack python skills, but I
> do want to help the portage team, as much as I can, to make this happen,
> as I have some great benefit from this added feature.
Whoever spear heads this is going to have to know at least a bit
python, so I'd suggest you learn- pretty straightforward. Would
suggest diveintopython.org for starters.
Portage however, is not, but if you have questions you are welcome to
ask in #-portage. Not saying we're going to do all of the legwork,
but we are available as a resource.
> Also, I hope I covered everything, and if the response from the mailing
> list is good I may consider revising the existing GLEP and prepare it
> for submittal to the council in feburary, or march, depending on how
> much revision the GLEP needs, and if my idea is better or worse then the
> current solution proposed.
Probably better to iron out what y'all actually need and what the dev
community is willing to put up with.
Eg, would do some research into it, read the archives from last few
wars over it, in general find (and address) the issues that lead to
glep19 going still born.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-06 5:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 4:42 [gentoo-dev] GLEP 19: Gentoo Stable Portage Tree -- ideas Andrew Muraco
2006-01-06 4:52 ` Andrew Muraco
2006-01-06 5:29 ` Brian Harring
2006-01-06 5:35 ` Brian Harring [this message]
2006-01-06 9:00 ` Chris Bainbridge
2006-01-06 9:36 ` [gentoo-dev] " Duncan
2006-01-06 15:09 ` Chris Gianelloni
2006-01-06 15:27 ` Lance Albertson
2006-01-06 16:19 ` Carsten Lohrke
2006-01-06 18:59 ` Chris Gianelloni
2006-01-06 16:46 ` Grant Goodyear
2006-01-06 17:12 ` Grant Goodyear
2006-01-08 0:24 ` Stuart Herbert
2006-01-06 17:25 ` Brian Harring
2006-01-06 18:41 ` Donnie Berkholz
2006-01-06 18:57 ` Chris Gianelloni
2006-01-06 15:05 ` [gentoo-dev] " Chris Gianelloni
2006-01-06 17:39 ` Brian Harring
2006-01-06 19:30 ` Chris Gianelloni
2006-01-06 22:48 ` [gentoo-dev] " Duncan
2006-01-06 23:32 ` Lance Albertson
2006-01-08 14:14 ` Chris Gianelloni
2006-01-08 16:55 ` Lance Albertson
2006-01-08 17:19 ` Brian Harring
2006-01-08 17:26 ` Lance Albertson
2006-01-06 23:11 ` [gentoo-dev] " Olivier Crete
2006-01-08 14:12 ` 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=20060106053556.GD28075@nightcrawler.e-centre.net \
--to=ferringb@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