public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Christopher Faylor <me@cgf.cx>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Current Status of Insight
Date: Fri, 13 May 2005 02:19:00 -0000	[thread overview]
Message-ID: <1115950737.4491.95.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <20050513020929.GB14106@trixie.casa.cgf.cx>

On Thu, 2005-05-12 at 22:09 -0400, Christopher Faylor wrote:
> I think past and current employees of Red Hat would probably agree with
> you about this sorry state of affairs.
> 
> Keith, what about a petition to Red Hat?  Think that would work?

I have no idea. For all I know, it might get me fired! [Okay, I don't
actually think it would, but who the heck knows?] I've thought about
this and other things.

I know this looks very badly upon Red Hat, but I want to make it
absolutely clear: I don't blame them one darn bit for not wanting to
take the time (and money) to see all the paperwork done. It does not
make economic sense.

I would also like to emphasize that when it comes to programming tools
(compilers, debuggers, etc), Red Hat is not a company, IME, that is all
take an no give. I've been involved with several projects where Red Hat
took AND gave back to the community.

Once again, I think we're finally at the point where we must ask
ourselves: Does it matter to anyone?*

Keith

* A question I have been meaning to ask for almost two years, but kept
chickening out in the last second...

  reply	other threads:[~2005-05-13  2:19 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12 10:07 Steven Johnson
2005-05-12 10:13 ` Jon Beniston
     [not found]   ` <2636500f05051203276a294e8f@mail.gmail.com>
2005-05-12 10:29     ` Nickolay Kolchin
2005-05-12 15:17 ` Keith Seitz
2005-05-12 21:46   ` Steven Johnson
2005-05-12 22:42     ` Duane Ellis
2005-05-12 22:45     ` Duane Ellis
2005-05-13  2:09     ` Christopher Faylor
2005-05-13  2:19       ` Keith Seitz [this message]
2005-05-13 13:53         ` Steven Johnson
2005-05-13 14:05           ` Christopher Faylor
2005-05-13 14:18             ` Jon Beniston
2005-05-13 14:21               ` Christopher Faylor
2005-05-13 14:16           ` Hans W. Horn
2005-05-13 14:29             ` Christopher Faylor
2005-05-13 14:33           ` James Lemke
2005-05-14 11:14           ` Nickolay Kolchin
2005-05-17 12:51             ` Fernando Nasser
2005-05-16 22:07         ` Steven Johnson
2005-05-13  1:15 Paul Schlie
2005-05-13  8:14 Roland Schwingel
     [not found] <1115992411.3092.ezmlm@sources.redhat.com>
2005-05-13 15:44 ` E. Weddington
2005-05-13 17:15   ` Christopher Faylor
2005-05-13 17:35     ` Bernhard Walle
2005-05-13 17:45       ` Christopher Faylor
2005-05-13 17:58         ` Bernhard Walle
2005-05-13 21:51           ` Fernando Nasser
2005-05-14 14:54             ` Duane Ellis
2005-05-14 17:25               ` Bernhard Walle
2005-05-17 19:38               ` Fernando Nasser
2005-05-14 22:13 Paul Schlie
2005-05-16  5:35 ` Steven Johnson
2005-05-17 19:33   ` Fernando Nasser
2005-05-16 16:10 ` Christopher Faylor
2005-05-16 17:18   ` Paul Schlie
2005-05-16 23:45 Paul Schlie
2005-05-17  8:26 Roland Schwingel
2005-05-17 10:18 ` Steven Johnson

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=1115950737.4491.95.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=me@cgf.cx \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).