From: Steven Johnson <sjohnson@sakuraindustries.com>
To: Roland Schwingel <roland.schwingel@onevision.de>
Cc: insight@sources.redhat.com
Subject: Re: Current Status of Insight
Date: Tue, 17 May 2005 10:18:00 -0000 [thread overview]
Message-ID: <428AFB2F.9030505@sakuraindustries.com> (raw)
In-Reply-To: <4289AA51.8080905@onevision.de>
Roland Schwingel wrote:
> Hi...
>
> Christopher Faylor wrote on 16.05.2005 18:08:44:
>
> > The project is only "dead" because no one is actively caring for it.
> > Making it part of gdb does not mean that someone will magically appear
> > to keep it alive. You still need people to do that.
> >
> > We CAN fix this. All that we need are volunteers to keep insight
> > healthy. While it would be nice to have insight officially part of
> gdb,
> > it has managed to survive fairly well for a long time in its present
> > state.
>
> As many others I am interested in keeping Insight alive and prospering.
> Unfortunately my knowledge of tcl/tk is only of experimental nature, so
> I might be not of much help there but (with limited time - I also need
> to talk to my employer first) I could maybe do something here and there.
Many of us fall into that basket (tcl/tk being an unknown quantity),
Myself included. Although i find that by looking at what is there
already, and using a good reference, the arcane nature of its syntax
becomes understandable. I tend to say "what do i need to do" and "what
can i find that looks like it does this for some other purpose, that i
can adapt". I tend to achieve most of what i want with this method.
Steven
next prev parent reply other threads:[~2005-05-17 10:18 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 8:26 Roland Schwingel
2005-05-17 10:18 ` Steven Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-16 23:45 Paul Schlie
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
[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-13 8:14 Roland Schwingel
2005-05-13 1:15 Paul Schlie
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
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
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=428AFB2F.9030505@sakuraindustries.com \
--to=sjohnson@sakuraindustries.com \
--cc=insight@sources.redhat.com \
--cc=roland.schwingel@onevision.de \
/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).