public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Patrick Monnerat" <Patrick.Monnerat@datasphere.ch>
To: "Keith Seitz" <keiths@redhat.com>
Cc: <insight@sourceware.org>
Subject: RE: Is the project still alive ?
Date: Wed, 23 Jul 2014 10:14:00 -0000	[thread overview]
Message-ID: <AB5E58B87EB73C46A38073D8F459F113D9FEE5@dataspheresrv01> (raw)
In-Reply-To: <53CEA351.4090002@redhat.com>

Keith Seitz wrote:

>> By the way: @Keith: did you received the tarball of my git repo ? 
>> Maybe this is time to publish or update or comment or... reject it.

> Yeah, I have received it, but because of my recent tendinitis
problems, I have zero time for play. All my free/play time is scheduled
for rest. :-(

I'm really sorry for you your tendinitis does not go away. In the
meantime, you can give me write access to the sourceware git repository:
I'll upload my "work in progress" there and so we'll have a common
reference base. Of course, if you don't like it you can zap it after
all: in any case there will be no damage to what officially exists yet
because the git repo is currently empty.

> I will do my best to take a look at what you've done. It sounds like
you're headed in a direction that encompasses the "ideal" build for
insight. Perhaps I can attempt to define some sort of extension API for
gdb to cleanup the rest. [But I seriously doubt that (some) gdb
maintainers would allow this.]

I don't think there's an "ideal" solution, with regards to the project
structure. In a modern approach, we should not deal with bundles and
"third part" code should be independent libraries. We could decide to do
so with (i)tcl/tk and iwidgets and even with libgui (by having it as a
project by itself). But gdb is definitely not such an API library, and
it has itself a bundled structure. Thus what you call "ideal" is just
the less bad compromise :-/

Regards,
Patrick

  reply	other threads:[~2014-07-23 10:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 11:28 Patrick Monnerat
2014-06-24 17:25 ` Bruce Dawson
2014-06-25 22:52 ` Keith Seitz
2014-06-26 10:15   ` Patrick Monnerat
2014-07-22 17:18   ` Tom Tromey
2014-07-22 17:42     ` Patrick Monnerat
2014-07-22 17:46       ` Keith Seitz
2014-07-23 10:14         ` Patrick Monnerat [this message]
2014-09-04  5:54 ` Pavel Fedin
2014-09-04  8:01   ` Richard Tierney
2014-09-04 12:39   ` Fernando Nasser
2014-06-25  5:44 Roland Schwingel
2014-06-25 10:43 ` Patrick Monnerat

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=AB5E58B87EB73C46A38073D8F459F113D9FEE5@dataspheresrv01 \
    --to=patrick.monnerat@datasphere.ch \
    --cc=insight@sourceware.org \
    --cc=keiths@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).