public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>,
		Insight List <insight@sources.redhat.com>
Subject: Re: insight build, plus patch request
Date: Tue, 15 Jul 2008 09:56:00 -0000	[thread overview]
Message-ID: <487C73C8.9060601@st.com> (raw)
In-Reply-To: <487BAD18.8040607@redhat.com>

Keith Seitz wrote:
> Tom Tromey wrote:
>> FYI -- Insight isn't building for me.  I'm using gdb cvs head as of a
>> day or two ago.

> Actually, it hasn't been building in several weeks. No one has noticed 
> yet... [Okay, you and one other person.]

> Methinks Insight's usefulness is coming to an end.

FWIW, ST still does ship Insight. I know that we have customers that do 
use it too, because we occasionally get support requests. Not too many 
though - it mostly Just Works. :)

All the new exciting work is going into the Eclipse product, but with 
that we're getting complaints that it's not enough like Insight! For one 
thing, the customers like the speed and simplicity.

We don't use CVS HEAD, so we don't scream the moment it breaks, but if 
there were no Insight 6.9 you'll probably hear about it. ;)

I can't offer much in the way of expertise or effort, but please take 
this as a vote for keeping Insight alive.

Thanks for all your hard work

Andrew

      parent reply	other threads:[~2008-07-15  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 19:35 Tom Tromey
2008-07-14 19:47 ` Keith Seitz
2008-07-14 20:30   ` Tom Tromey
2008-07-14 20:43     ` Keith Seitz
2008-07-14 20:54       ` Tom Tromey
2008-07-15  9:56   ` Andrew STUBBS [this message]

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=487C73C8.9060601@st.com \
    --to=andrew.stubbs@st.com \
    --cc=insight@sources.redhat.com \
    --cc=keiths@redhat.com \
    --cc=tromey@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).