From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 7.6 released!
Date: Mon, 06 May 2013 10:32:00 -0000 [thread overview]
Message-ID: <20130506103203.GC5278@adacore.com> (raw)
In-Reply-To: <20130505194406.GA15079@host2.jankratochvil.net>
> While according to the GDB rules the throw_perror_with_name function
> could be removed now (merged back into perror_with_name) I do not find
> it completely right, throw_perror_with_name is a logical part in the
> whole error reporting set and it is only coincidence it has currently
> no users.
I had a feeling that we'd feel that way. No problem with that on my end.
--
Joel
next prev parent reply other threads:[~2013-05-06 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20130426140741.GA13837@adacore.com>
[not found] ` <83k3nptk18.fsf@gnu.org>
2013-04-28 22:59 ` Eli Zaretskii
2013-04-29 9:53 ` Joel Brobecker
2013-04-29 12:48 ` Eli Zaretskii
2013-04-29 14:37 ` Joel Brobecker
2013-04-29 15:24 ` Andreas Schwab
2013-05-05 19:44 ` Jan Kratochvil
2013-05-06 10:32 ` Joel Brobecker [this message]
2013-05-06 16:19 ` Eli Zaretskii
2013-05-06 18:19 ` Tom Tromey
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=20130506103203.GC5278@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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