From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>,
"Joseph S. Myers" <joseph@codesourcery.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: GDB 6.7 branch creation scheduled June 10th
Date: Thu, 14 Jun 2007 18:58:00 -0000 [thread overview]
Message-ID: <20070614185812.GA16497@caradoc.them.org> (raw)
In-Reply-To: <1181847058.6629.10.camel@localhost.localdomain>
On Thu, Jun 14, 2007 at 03:50:58PM -0300, Thiago Jung Bauermann wrote:
> I posted this patch to the list a while back:
>
> http://sourceware.org/ml/gdb-patches/2007-04/msg00359.html
>
> If the patch is ok, I'd like to ask for its inclusion in GDB 6.7.
I believe Joseph was looking at this patch earlier, and it was not
working properly for him. Joseph, was that the same patch?
Further comments, please reply to the patch instead of this message,
please.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-14 18:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 6:18 Joel Brobecker
2007-06-08 6:39 ` Nick Roberts
2007-06-11 1:23 ` Daniel Jacobowitz
2007-06-14 18:54 ` Thiago Jung Bauermann
2007-06-14 18:58 ` Daniel Jacobowitz [this message]
2007-06-14 23:42 ` Joseph S. Myers
2007-06-21 18:13 ` DELAYED: GDB 6.7 branch creation scheduled June 25th Joel Brobecker
2007-06-21 18:22 ` H. J. Lu
2007-06-21 21:47 ` Nick Roberts
2007-06-22 1:39 ` Joel Brobecker
2007-06-22 7:23 ` Nick Roberts
2007-06-22 16:16 ` Joel Brobecker
2007-06-23 0:08 ` Nick Roberts
2007-06-23 0:34 ` Joel Brobecker
2007-06-23 0:58 ` Nick Roberts
2007-06-23 1:22 ` Joel Brobecker
2007-06-23 1:43 ` Nick Roberts
2007-06-23 4:44 ` Joel Brobecker
2007-06-24 0:44 ` Nick Roberts
2007-06-24 1:57 ` Daniel Jacobowitz
2007-06-25 23:54 ` Joel Brobecker
2007-06-26 19:00 ` Joel Brobecker
2007-06-26 19:15 ` Markus Deuling
2007-06-23 12:33 ` Daniel Jacobowitz
2007-06-22 20:14 ` Stan Shebs
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=20070614185812.GA16497@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=joseph@codesourcery.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