From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: GLEP 19: Gentoo Stable Portage Tree -- ideas
Date: Fri, 06 Jan 2006 13:59:12 -0500 [thread overview]
Message-ID: <1136573952.18383.67.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <200601061719.13224.carlo@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
On Fri, 2006-01-06 at 17:19 +0100, Carsten Lohrke wrote:
> On Friday 06 January 2006 16:27, Lance Albertson wrote:
> > As seen from the discussion earlier this week, I don't think Gentoo has
> > the proper open-mindness to create a proper enterprise distro.
>
> This has nothing to with open-mindness, but having enough people doing the
> general maintenance of a clearly defined frozen (sub-)tree as well as
> backports to fix vulnerabilities and other critical issues, without negative
> effects on other Gentoo subprojects (like "I work now on GLEP 19 stuff and
> don't care what I leave unmaintained instead."). Don't expect that
> maintainers of packages of the current tree do backports for a GLEP 19 tree.
> This is something the proponents would need to do themselves. You can't
> expect a commitment of the whole developer crowd in something only a minority
> is interested in. This doesn't mean there can't be a frozen tree within the
> context of Gentoo or as a separate project, of course.
Exactly. I'm finishing up my proofreading and spell-checking and should
be sending out my little idea within the hour.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-06 19:05 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
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 [this message]
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=1136573952.18383.67.camel@cgianelloni.nuvox.net \
--to=wolf31o2@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