From: nickrob@snap.net.nz (Nick Roberts)
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] PR backtrace/9786
Date: Tue, 21 Apr 2009 08:28:00 -0000 [thread overview]
Message-ID: <18925.33714.758790.276557@totara.tehura.co.nz> (raw)
In-Reply-To: <m3k55f450c.fsf@fleche.redhat.com>
> I don't know anything about this patch, so I can't really answer
> that... but could you add this to the wiki as a release blocker?
> I think that's the best way to ensure that some decision is made
> before 7.0.
OK, thanks. I have done that.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2009-04-21 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 19:37 Nick Roberts
2009-02-23 0:51 ` Joel Brobecker
2009-02-23 1:08 ` Pedro Alves
2009-02-23 2:08 ` Daniel Jacobowitz
2009-04-18 0:43 ` Nick Roberts
2009-04-20 17:19 ` Tom Tromey
2009-04-21 8:28 ` Nick Roberts [this message]
2009-06-23 18:39 ` Joel Brobecker
2009-06-23 18:46 ` Daniel Jacobowitz
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=18925.33714.758790.276557@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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