From: Eli Zaretskii <eliz@gnu.org>
To: pgilliam@us.ibm.com
Cc: gdb@sources.redhat.com
Subject: Re: GDB paper accepted for GCC summit
Date: Sun, 19 Mar 2006 17:05:00 -0000 [thread overview]
Message-ID: <umzfovvrq.fsf@gnu.org> (raw)
In-Reply-To: <1142633147.21920.400.camel@dufur.beaverton.ibm.com> (message from PAUL GILLIAM on Fri, 17 Mar 2006 14:05:47 -0800)
> From: PAUL GILLIAM <pgilliam@us.ibm.com>
> Date: Fri, 17 Mar 2006 14:05:47 -0800
>
> Failing that, I would like suggestions of which developments I should
> research, using the News file, mailing lists, ChangeLog, and source code
> as the sources.
The NEWS file should be the starting point. We try to make a point of
mentioning there every noteworthy user-level change.
next prev parent reply other threads:[~2006-03-18 11:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-18 11:13 PAUL GILLIAM
2006-03-19 17:05 ` Eli Zaretskii [this message]
2006-03-30 0:32 ` PAUL GILLIAM
2006-03-30 1:41 ` Randolph Chung
2006-03-30 4:13 ` Daniel Jacobowitz
2006-03-30 22:42 ` Mark Kettenis
2006-03-30 1:36 ` GDB paper for GCC summit: New Commands PAUL GILLIAM
2006-03-30 4:30 ` Joel Brobecker
2006-04-01 13:21 ` Eli Zaretskii
2006-04-10 22:27 ` GDB paper at GCC summit: user-level features PAUL GILLIAM
2006-04-11 9:01 ` GDB paper accepted for GCC summit PAUL GILLIAM
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=umzfovvrq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=pgilliam@us.ibm.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