From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: time to release soon? GDB 8.1.1 release 2018-05-14 update
Date: Fri, 18 May 2018 00:32:00 -0000 [thread overview]
Message-ID: <87r2ma2csw.fsf@tromey.com> (raw)
In-Reply-To: <20180517172317.rtfaa3aoluse3gtd@adacore.com> (Joel Brobecker's message of "Thu, 17 May 2018 10:23:17 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> Agreed that the second patch is a little invasive. Looking at the first
Joel> one, it seems very localized, and can only affect Rust. If you feel
Joel> confident that the patch is safe, we could just create a PR number
Joel> for this issue, add it to the ChangeLog and revision log, and then
Joel> use version #1 for the 8.1 branch.
If the DWARF reader patch goes in 8.1, then I will do that.
Otherwise I probably won't. I'm not very concerned about -readnow; I
think pretty much only gdb developers use it or should use it.
Tom
next prev parent reply other threads:[~2018-05-17 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 17:59 Joel Brobecker
2018-05-17 16:19 ` Tom Tromey
2018-05-17 20:37 ` Joel Brobecker
2018-05-18 0:32 ` Tom Tromey [this message]
2018-05-18 19:14 ` Joel Brobecker
2018-05-18 19:50 ` 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=87r2ma2csw.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).