From: "Kent Fredric" <kentfredric@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Again: Critical bugs considered invalid
Date: Sat, 9 Jun 2007 22:19:31 +1200 [thread overview]
Message-ID: <8cd1ed20706090319o6203ec2akbddf1601536e6d0c@mail.gmail.com> (raw)
In-Reply-To: <466A76F2.9010909@exceedtech.net>
On 6/9/07, Dale <dalek@exceedtech.net> wrote:
> Kent Fredric wrote:
> > On 6/9/07, Zachary Grafton <zachary.grafton@gmail.com> wrote:
> >> On Friday 08 June 2007 19:29, Hemmann, Volker Armin wrote:
> >>
> >> Maybe someone should submit a bug report....
> >
> > http://www.xkcd.com/c258.html
> >
> > I tried . Critical bug, but was considered 'invalid' by the
> > prayer-wranglers.
> >
> >
> >
>
> Let me guess, Jakub closed it? LOL
>
> Can I also assume he decided to stay? I read he was leaving a while back.
>
> Dale
>
> :-) :-) :-)
Lemme be perfectly clear here. Jakub does a very good job of what he
does, and gentoo IMO does suffer a bit when hes not here. Bugs need
wrangling, or the right devs dont get even told they're there, and
Jakub does a legendary job of redirecting them to the right place.
Its like having an email server with only one ingoing email address
and having to get a human to redirect all the mails by hand to the
right inboxes.
He is like gentoo. Not perfect, but better than all the other choices :)
Gentoo does tend to get a little pissy sometimes, but what can you expect =)
--
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print "enNOSPicAMreil kdrtf@gma.com"[(2*x)..(2*x+1)]}'
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-09 10:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 23:34 [gentoo-user] Again: Critical bugs considered invalid Davi
2007-06-07 0:01 ` Enrico Weigelt
2007-06-07 23:21 ` b.n.
2007-06-08 7:57 ` [gentoo-user] " Alexander Skwar
2007-06-08 10:39 ` b.n.
2007-06-08 12:40 ` Hemmann, Volker Armin
2007-06-08 22:29 ` »Q«
2007-06-08 23:29 ` Hemmann, Volker Armin
2007-06-09 6:49 ` Zachary Grafton
2007-06-09 9:05 ` Kent Fredric
2007-06-09 9:46 ` Dale
2007-06-09 10:19 ` Kent Fredric [this message]
2007-06-09 13:11 ` Dale
2007-06-09 13:24 ` Dale
2007-06-09 17:42 ` Bo Ørsted Andresen
2007-06-10 1:30 ` Dale
2007-06-08 14:04 ` [gentoo-user] " Enrico Weigelt
2007-06-08 23:25 ` b.n.
2007-06-12 17:08 ` Enrico Weigelt
2007-06-12 19:25 ` Kent Fredric
-- strict thread matches above, loose matches on Subject: below --
2007-06-05 15:07 Enrico Weigelt
2007-06-05 15:45 ` Hemmann, Volker Armin
2007-06-06 21:51 ` Enrico Weigelt
2007-06-06 22:01 ` Hemmann, Volker Armin
2007-06-06 23:10 ` Enrico Weigelt
2007-06-07 7:11 ` [gentoo-user] " Alexander Skwar
2007-06-07 7:10 ` Alexander Skwar
2007-06-05 15:48 ` [gentoo-user] " Hans-Werner Hilse
2007-06-06 22:03 ` Enrico Weigelt
2007-06-07 2:58 ` [gentoo-user] " »Q«
2007-06-06 7:14 ` Alexander Skwar
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=8cd1ed20706090319o6203ec2akbddf1601536e6d0c@mail.gmail.com \
--to=kentfredric@gmail.com \
--cc=gentoo-user@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