public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bernhard.walle@gmx.de>
To: insight@sources.redhat.com
Subject: Re: Current Status of Insight
Date: Fri, 13 May 2005 17:35:00 -0000	[thread overview]
Message-ID: <d62nuo$5ep$1@sea.gmane.org> (raw)
In-Reply-To: <20050513171503.GB20585@trixie.casa.cgf.cx>

Hello,

* Christopher Faylor [13.05.2005 19:15]:
> 
> This is now the second time I've made this observation but people still
> seem to just be responding to the "who's interested" aspect of this
> discussion.  To me that's like asking how many people at a ball park are
> there because they're interested in watching a ball game.  Of course
> everyone here is interested in insight.  The question is what are you
> going to devote to keeping insight alive and healthy?

Maybe you or someone else which is able to do that can put an
announcement on the Insight website that developers are needed, what to
do and how to get in contact.

I think this mailing list has a small audience. But: Insight is used in
the embedded segment, and there's no real (GUI) alternative on Windows.
DDD is good but needs X11 and GVD doesn't exist any more.


> Btw, I notice an executable in the download area of winavr but I don't
> see any source code downloads.  The GPL requires that you provide the
> source code for any executables that you provide.  Pointing to another
> web site is not enough, you have to provide the sources.  Maybe the
> source code is actually part of the .exe, though, if that is the case
> then nevermind.

Can you contact WinAVR people? I'm sure they can solve the problem!


Regards,
 Bernhard

-- 

  reply	other threads:[~2005-05-13 17:35 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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-17  8:26 Roland Schwingel
2005-05-17 10:18 ` Steven Johnson
  -- 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
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='d62nuo$5ep$1@sea.gmane.org' \
    --to=bernhard.walle@gmx.de \
    --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).