From: Daniel Jacobowitz <drow@false.org>
To: Nicholas Mc Guire <hofrat@hofr.at>
Cc: Eli Zaretskii <eliz@gnu.org>,
Joel Brobecker <brobecker@adacore.com>,
gdb@sourceware.org
Subject: Re: Our next GDB release (GDB version 6.8)
Date: Sun, 27 Jan 2008 15:10:00 -0000 [thread overview]
Message-ID: <20080127151016.GA1750@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0801262330270.1751@vlab.hofr.at>
On Sat, Jan 26, 2008 at 11:37:44PM -0900, Nicholas Mc Guire wrote:
>
>
> > > Date: Fri, 25 Jan 2008 16:53:19 -0800
> > > From: Joel Brobecker <brobecker@adacore.com>
> > >
> > > I would like us to start drawing a list of things that we'd like
> > > to include in that release. For one, I'd like to list the changes
> A bit off topic maybe - but I would like to know if it would be posible
> to include the tracepoints implementation we did for gdb 6.3,6.4,6.5,6.6
> as maintaining it off-tree is a bit of a wast of energy and time
> A first port for CELL PPE/SPU is also available.
>
> The gdb tracepoint patches + manual can be found at:
> ftp://dslab.lzue.du.cn:/pub/tracepoints/
That URL does not exist...
> pleas let me know if this is posible and what we need to do to make this
> happen.
As with any contribution, the first step is copyright assignment - the
author needs to contact the FSF. If you're interested in doing this,
let me know and I can send you the form. Then the second step is to
post the changes to gdb-patches.
I don't think anything large will make 6.8 at this date but there's
always another release.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-01-27 15:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 0:53 Joel Brobecker
2008-01-26 9:21 ` Eli Zaretskii
2008-01-26 13:59 ` Joel Brobecker
2008-01-26 14:14 ` Eli Zaretskii
2008-01-26 16:07 ` Joel Brobecker
2008-01-26 16:36 ` Eli Zaretskii
2008-01-26 17:00 ` Christopher Faylor
2008-01-26 17:19 ` Eli Zaretskii
2008-01-26 17:25 ` Joel Brobecker
2008-01-26 17:19 ` Joel Brobecker
2008-01-27 7:32 ` Nicholas Mc Guire
2008-01-27 15:10 ` Daniel Jacobowitz [this message]
[not found] ` <Pine.LNX.4.58.0801282316360.2555@vlab.hofr.at>
2008-01-29 13:50 ` Daniel Jacobowitz
2008-01-29 20:23 ` Eli Zaretskii
2008-01-27 17:05 ` Jim Blandy
2008-01-28 10:56 ` Pierre Muller
2008-01-28 12:35 ` Pedro Alves
2008-01-28 12:41 ` Pedro Alves
2008-01-28 17:40 ` Paul Koning
2008-01-31 14:49 ` Pedro Alves
2008-01-28 21:02 ` Thiago Jung Bauermann
2008-01-29 21:19 ` Joel Brobecker
2008-01-30 10:57 ` Markus Deuling
2008-01-30 18:32 ` Joel Brobecker
2008-01-30 23:14 ` Doug Evans
2008-01-31 0:09 ` Joel Brobecker
2008-01-31 8:15 ` Vladimir Prus
2008-01-31 16:55 ` Joel Brobecker
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=20080127151016.GA1750@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=hofrat@hofr.at \
/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