From: Thilo Bangert <bangert@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Reviving GLEP33
Date: Thu, 12 Aug 2010 11:06:21 +0200 [thread overview]
Message-ID: <201008121106.23780.bangert@gentoo.org> (raw)
In-Reply-To: <AANLkTi=_+L9YeOHapz7GxsdNVhw+0cnB92Uw7JSUouWR@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1628 bytes --]
Ben de Groot <yngwin@gentoo.org> said:
> On 7 August 2010 02:18, Brian Harring <ferringb@gmail.com> wrote:
> > The thing you're ignoring out of this g55 idiocy is that people don't
> > particularly seem to want it. There has been an extremely vocal
> > subgroup of paludis/exherbo devs pushing for it while everyone else
> > seems to have less than an interest in it. That's generalizing a
> > bit, but is reasonably accurate.
>
> Exactly. This is Gentoo. Let Exherbo devs go develop their own distro
> and stop trying to interfere with Gentoo. It is time the council puts
> a definite stop to GLEP 55.
if the council should stop anything, then rude behavior like you have
shown. I am personally much in favor for GLEP55, as it solves a technical
problem that keeps coming up and have no association with Exherbo at all.
If you want to constructively contribute to Gentoo, i'd hope you
reconsider a message like the above before sending it next time.
>
> > _EITHER WAY_, rather than having g33 get beat down for unrelated
> > reasons by people screaming they want their pony/g55, g33 can proceed
> > despite claims to the contrary, and it doesn't require g55 as
> > ciaran/crew have claimed.
>
> I for one am a strong supporter of GLEP 33. I believe it is one of the
> most promising ways to move forward. And I hope the council decides to
> get behind this.
I for one am a strong supporter of GLEP 55. I believe it is one of the
most promising ways to move forward. And I hope the council decides to
get behind this.
I also support the aims of GLEP33.
>
> Cheers,
> Ben
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-08-12 9:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 9:56 [gentoo-dev] RFC: Reviving GLEP33 Matti Bickel
2010-08-02 11:11 ` Brian Harring
2010-08-02 18:16 ` David Leverton
2010-08-02 21:40 ` Matti Bickel
2010-08-02 22:17 ` David Leverton
2010-08-02 23:10 ` Matti Bickel
2010-08-02 19:51 ` Mike Frysinger
2010-08-02 21:47 ` Matti Bickel
2010-08-02 22:10 ` Mike Frysinger
2010-08-03 7:32 ` Ciaran McCreesh
2010-08-02 20:15 ` Ciaran McCreesh
2010-08-02 21:55 ` Matti Bickel
2010-08-03 7:35 ` Ciaran McCreesh
2010-08-05 3:27 ` Brian Harring
2010-08-05 17:22 ` Matti Bickel
2010-08-05 23:43 ` Jeremy Olexa
2010-08-06 11:04 ` [gentoo-dev] " Duncan
2010-08-06 3:52 ` [gentoo-dev] " Brian Harring
2010-08-06 16:15 ` David Leverton
2010-08-06 17:27 ` Brian Harring
2010-08-06 17:48 ` Ciaran McCreesh
2010-08-06 18:18 ` Brian Harring
2010-08-06 18:34 ` Ciaran McCreesh
2010-08-12 18:04 ` Brian Harring
2010-08-12 7:51 ` Ben de Groot
2010-08-12 8:13 ` Ciaran McCreesh
2010-08-12 9:06 ` Thilo Bangert [this message]
2010-08-12 12:04 ` David Leverton
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=201008121106.23780.bangert@gentoo.org \
--to=bangert@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