public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Steven Johnson <sjohnson@sakuraindustries.com>
To: insight@sources.redhat.com
Subject: Current Status of Insight
Date: Thu, 12 May 2005 10:07:00 -0000	[thread overview]
Message-ID: <428460FB.3090607@sakuraindustries.com> (raw)

Hi, ive been away from Insight for quite some time.

Correct me (and maybe forgive me) if i make any errors, the following is 
from my memory, and i do not wish to upset anyone.

I seem to recall there was a falling out between FSF and Redhat over 
Insight. (I do not know exactly what about, and if i did i wouldnt have 
a position either way) and at about the same time (V5.3) vintage (around 
2 years ago) Insight stopped being
(a) actively developed and
(b) released in synch with the GDB mainline.

There was a time when GDB X.YY would be released and insight X.YY seemed 
to be there right along with it, that was a long time ago now.

My email is basically a query on the status, is Insight alive and well?

Is the FSF/Redhat thing over Insight resolved?

Is there a road map for re-synching Insight with GDB releases, so people 
dont get stuck using an over 2 year old version (cause the web site says 
thats the latest stable version).  Telling people to use CVS_HEAD is 
hardly ideal.  It doesnt really inspire confidence in stability.  
Although I understand that might be the best answer anyone can currently 
give.

Or should I use DDD (which i dont really like, because i think Motif 
must have been designed by people that had no eyes, and was then hit 
with the ugly stick 3 times on birth. [Personal opinion, Motif guys if 
you like how it looks, more power to you])

Is Insight CVS_HEAD currently in-synch with GDB 6.3?  If so, could an 
Insight 6.3 be cut and released as a stable version?  If not whats the 
impediment?

Im happy to do the checking out and packaging of the source (if someone 
can tell me the appropriate CVS tag to use), and web site updating if 
thats all it requires.

Steven Johnson


             reply	other threads:[~2005-05-12 10:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12 10:07 Steven Johnson [this message]
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
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=428460FB.3090607@sakuraindustries.com \
    --to=sjohnson@sakuraindustries.com \
    --cc=insight@sources.redhat.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).