Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Andrew J. Hutton" <ajh@gccsummit.org>
To: Kris Warkentin <kewarken@qnx.com>
Cc: Andrew Cagney <ac131313@redhat.com>,
	Daniel Jacobowitz <drow@mvista.com>,
	gdb@sources.redhat.com
Subject: Re: Is anyone going to the GCC summit?
Date: Wed, 19 Mar 2003 19:18:00 -0000	[thread overview]
Message-ID: <1048101485.4122.8.camel@penguin> (raw)
In-Reply-To: <04b501c2ee46$a77ddc00$0202040a@catdog>

On Wed, 2003-03-19 at 13:37, Kris Warkentin wrote:
> > To be honest, it currently looks a little too GCC centric :-(  Broadened
> > a little, so that it covered BINUTILS and GDB would definitly make it
> > more appealing.
> 
> We have 5 people going and quite a few of us have mostly gdb/binutils
> interest.  We're sending a large contingent since we're headquartered in
> Ottawa.  Perhaps if we get a critical mass of gdb people, we might be able
> to form a working group to discuss some current gdb issues.
> 
> I'm wondering if the organizers might be interested in broadening it
> somewhat to be more of a 'GNU Devtools Summit'.  It's probably a little late
> at this stage of the game but if we could manage even a few informal things
> at this one, perhaps it could sow the seed for future summits.

This was always the intent of the event as a whole, the announcement on
the site tries to make this clear.

-- 
GCC Developer's Summit, May 25th-27th, 2003, Ottawa, Canada
For Developer's and Users of the GNU Compiler Collection

Join the new GCC developer's IRC channel #gcc at irc.oftc.net


      reply	other threads:[~2003-03-19 19:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 17:07 Daniel Jacobowitz
2003-03-12 20:42 ` Jason Molenda
2003-03-19 18:27 ` Andrew Cagney
2003-03-19 18:37   ` Kris Warkentin
2003-03-19 19:18     ` Andrew J. Hutton [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=1048101485.4122.8.camel@penguin \
    --to=ajh@gccsummit.org \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=kewarken@qnx.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