public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 10.1 release -- 2020-09-18 Update
Date: Sat, 19 Sep 2020 21:03:41 -0400	[thread overview]
Message-ID: <72a2558b-bcad-ecd9-7311-b3ef799ccfd8@simark.ca> (raw)
In-Reply-To: <20200918234602.GA4674@adacore.com>

On 2020-09-18 7:46 p.m., Joel Brobecker wrote:
> Hello,
>
> A quick update on the release status since the 10.0.90 pre-release
> was published last Saturday...
>
> So far, we don't have anything really worrisome that could significantly
> delay the release. I'll try to find some time to test the gnulib patches
> that Eli pointed out next week.

I just filed this ("TUI focus behavior change"), if it's considered a
bug then I think it should be put on the list of blockers.

https://sourceware.org/bugzilla/show_bug.cgi?id=26638

Simon

  parent reply	other threads:[~2020-09-20  1:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 23:46 Joel Brobecker
2020-09-19  1:37 ` Simon Marchi
2020-09-19 19:42   ` Joel Brobecker
2020-09-19 23:58     ` Simon Marchi
2020-09-19  7:41 ` Eli Zaretskii
2020-09-19 19:48   ` Joel Brobecker
2020-09-21 16:26     ` Eli Zaretskii
2020-09-26 17:39       ` Joel Brobecker
2020-09-28  9:30         ` Eli Zaretskii
2020-09-28 20:11           ` Joel Brobecker
2020-10-09 19:53             ` [pushed/gdb-10-branch] gnulib: fix stat/fstat build errors on old Windows version or using old MinGW Joel Brobecker
2020-09-20  1:03 ` Simon Marchi [this message]
2020-09-20  6:09   ` GDB 10.1 release -- 2020-09-18 Update Eli Zaretskii
2020-09-21 19:54 ` Simon Marchi
2020-09-23 13:39   ` Tom Tromey
2020-09-23 14:00     ` 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=72a2558b-bcad-ecd9-7311-b3ef799ccfd8@simark.ca \
    --to=simark@simark.ca \
    --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).