From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sources.redhat.com
Subject: Re: GDB 6.5 branch on Sun May 14th
Date: Sun, 14 May 2006 22:44:00 -0000 [thread overview]
Message-ID: <20060514212853.GA7712@nevyn.them.org> (raw)
In-Reply-To: <17512.61703.762754.414587@kahikatea.snap.net.nz>
On Tue, May 16, 2006 at 09:22:15AM +1200, Nick Roberts wrote:
> OK, I had thoght you considered the change to be reasonable. Lets leave it
> till after the release then, when we can discuss how to print values more
> fully. As Eli points out, its pretty pointless trying to predict Emacs's
> release anyway.
I'll get to it before the release if I can; it's just that GDB builds
up such a backlog of unreviewed patches that it takes a full day or
more every time I get started.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-14 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 6:57 Joel Brobecker
2006-05-14 7:33 ` Nick Roberts
2006-05-14 10:41 ` Joel Brobecker
2006-05-14 16:03 ` Daniel Jacobowitz
2006-05-14 22:38 ` Nick Roberts
2006-05-14 22:44 ` Daniel Jacobowitz [this message]
2006-05-14 21:29 ` Eli Zaretskii
2006-05-14 16:40 ` Daniel Jacobowitz
2006-08-22 9:51 Nick Roberts
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=20060514212853.GA7712@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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