From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, Keith Seitz <keiths@redhat.com>
Subject: Re: GDB 8.1.1 release -- 2018-07-26 update
Date: Mon, 30 Jul 2018 16:06:00 -0000 [thread overview]
Message-ID: <20180730160627.GA3511@adacore.com> (raw)
In-Reply-To: <87effo7myy.fsf@tromey.com>
> Joel> Given that this is just a couple of hours of my time, unless we're
> Joel> sure it would be useless, I propose we still go ahead with the 8.1.1
> Joel> release.
>
> I think any of these choices seems reasonable.
> Are there other things in 8.1.1 that would be release-worthy?
> If not I suppose that would narrow it down to "wait for 8.2".
Thanks for the feedback, Tom. The list of changes for 8.1.1 can
be found at this URL: https://sourceware.org/bugzilla/buglist.cgi?list_id=43335&product=gdb&query_format=advanced&resolution=FIXED&target_milestone=8.1.1
And that was a good suggestion, as it fixes a complete breakage
of GDBserver on Windows. And still speaking of GDBserver, there was
a small change of behavior that Sergio fixed as well.
So worth a release, I would say.
--
Joel
next prev parent reply other threads:[~2018-07-30 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 16:12 Joel Brobecker
2018-07-27 14:49 ` Tom Tromey
2018-07-30 16:06 ` Joel Brobecker [this message]
2018-07-30 19:55 ` Simon Marchi
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=20180730160627.GA3511@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=tom@tromey.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