public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: frysk <frysk@sources.redhat.com>
Subject: C++ debugger mailing list
Date: Fri, 04 Jul 2008 20:32:00 -0000	[thread overview]
Message-ID: <486E887B.9020707@redhat.com> (raw)

I'd like to propose that discussions and planning for this new project 
(or rebooted frysk as some have called it) be on a dedicated mailing 
list (it can be bootstrapped using frysk's membership), and then we 
extend a hand to gdb@ developers inviting them to participate.

I think an invitation to interested gdb developers to something clearly 
not frysk and not gdb, would be a strong symbolic gesture to all 
concerned that the intent here is inclusion.

Andrew

             reply	other threads:[~2008-07-04 20:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04 20:32 Andrew Cagney [this message]
2008-07-07 18:55 ` Elena Zannoni
2008-07-07 20:08   ` Tom Tromey
2008-07-08 13:40   ` Andrew Cagney

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=486E887B.9020707@redhat.com \
    --to=cagney@redhat.com \
    --cc=frysk@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).