From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org, tdevries@suse.de,
cbiesinger@google.com, philippe.waroquiers@skynet.be,
andrew.burgess@embecosm.com
Subject: Re: GDB 9.1 release -- 2019-11-18 Update
Date: Tue, 19 Nov 2019 19:06:00 -0000 [thread overview]
Message-ID: <87lfsbwuri.fsf@tromey.com> (raw)
In-Reply-To: <878sobyhhl.fsf@tromey.com> (Tom Tromey's message of "Tue, 19 Nov 2019 09:10:30 -0700")
Joel> - [TomT] Fix the "winheight" command
Joel> https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/371
Joel> Fixes a regression.
Joel> Tom says it can be backported after branching if needed.
Tom> I'll send a smaller version of this that doesn't involve rewriting all
Tom> of the TUI layout code.
I think it's possible to just cherry-pick the final patch in that series.
So, I'll probably check it in later today, if testing it shows it is ok.
Tom
next prev parent reply other threads:[~2019-11-19 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 1:12 Joel Brobecker
2019-11-19 16:10 ` Tom Tromey
2019-11-19 19:06 ` Tom Tromey [this message]
2019-11-24 18:16 ` Philippe Waroquiers
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=87lfsbwuri.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--cc=brobecker@adacore.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
--cc=tdevries@suse.de \
/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).