From: Johan <insight@fun-tech.se>
To: Keith Seitz <keiths@redhat.com>
Cc: Ricard Wanderlof <ricard.wanderlof@axis.com>, insight@sourceware.org
Subject: Re: Re: Insight development?
Date: Thu, 06 May 2010 19:55:00 -0000 [thread overview]
Message-ID: <4BE31EB4.6010702@fun-tech.se> (raw)
In-Reply-To: <4BDEFC92.5050505@redhat.com>
Hi
Keith Seitz wrote:
>
> Active development has pretty much stopped entirely. As far as I know,
> I am the only person still actively trying to keep insight crawling
> along -- largely because I still use it daily for my work.
>
> Keith
>
It sounds like a troublesome situation,
and since I'm using it as a nice frontend for OpenOCD (arm jtag to gdb
server).
I hate to see it die.
Maybe it could be easier to get people to give a helping hand if the code
was more accessible? I thinking cvs vs. git/subversion question?
Maybe it is a good idea to start to use something like github.com?
By the way, how dependent on cvs is this project?
(Is there a lot of magic happening on the cvs-server?)
BR
Johan
prev parent reply other threads:[~2010-05-06 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 12:35 Ricard Wanderlof
2010-05-03 16:41 ` Keith Seitz
2010-05-03 18:58 ` Christopher Faylor
2010-05-06 19:55 ` Johan [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=4BE31EB4.6010702@fun-tech.se \
--to=insight@fun-tech.se \
--cc=insight@sourceware.org \
--cc=keiths@redhat.com \
--cc=ricard.wanderlof@axis.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).