public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Jim Ingham <jingham@apple.com>
Cc: insight@sources.redhat.com
Subject: Re: Cannot run from build directory
Date: Thu, 12 Oct 2000 09:55:00 -0000	[thread overview]
Message-ID: <39E5ECFD.6C9AD23D@cygnus.com> (raw)
In-Reply-To: <B60B2BF9.6C2F%jingham@apple.com>

Jim Ingham wrote:
> 
> Fernando,
> 
> Thanks for this AND all your other efforts on behalf of Insight!!!  I know
> pushing this issue forward is in great part your own initiative (and
> probably evenings too, though I hope not).  It is much appreciated!
> 

Insight is a very sexy debugger GUI.  It deserves some attention.

I would not be able to do anything alone.  I am getting lots of help.  I have been
bugging you and Keith a lot and I know that you guys have other responsibilities
in your respective companies.  You guys have also helped a lot with the list.
Thanks a lot!

Mo, have also helped a lot.  He has registered bugs, suggestions and helped people on the
list as well (despite all the work he has to do on Source Nav already). Syd is keeping our
version of Tcl/Tk and working a lot to move us to the latest version of things.  He also jumps in
for clarifications when these issues show up in the list.   Chris Faylor and
Tom Tromey have also helped with the list, among other things. Several folks from gdb land
have been helping tracking down bugs that are related to interactions between the GUI and
the core code. Not to mention the managers here at Red Hat who did all they could to allow
me to work on it.  I have bugged Karen, Chris and Eric a lot to get funding for Insight.
Thanks, thanks, thanks!

And there is more help coming now.  Other people from the net are becoming interested
and willing to help. There are already more people trying to help others in the list,
some people helping me track some bugs (I took the intermediate messages off the list to
minimize traffic) and people asking how they can contribute.  Thanks folks!

But we won't go far unless more people from the net jumps in. We will have to make working
in Insight easier for this to happen, but I guess this will come with continuous
maintenance.


P.S.: Yes, evenings too, unfortunately.  But I believe that is because of the backlog.
I hope it will soon get a little more bearable and as more people start to help with
fixing bugs, improvements and list help things will get back to normal.

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

  reply	other threads:[~2000-10-12  9:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <971299064.12857.ezmlm@sources.redhat.com>
2000-10-11 18:18 ` Jim Ingham
2000-10-11 19:05   ` Fernando Nasser
2000-10-12  8:48     ` Jim Ingham
2000-10-12  9:55       ` Fernando Nasser [this message]
2000-10-10 11:10 Syd Polk
2000-10-10 11:26 ` Duane Ellis

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=39E5ECFD.6C9AD23D@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=insight@sources.redhat.com \
    --cc=jingham@apple.com \
    /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).