From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: start of the GDB 11 release cycle
Date: Mon, 24 May 2021 12:40:41 -0700 [thread overview]
Message-ID: <20210524194041.GA758326@adacore.com> (raw)
In-Reply-To: <YJimYGbM/SBPeYwE@vapier>
Hi Mike,
> On 09 May 2021 17:04, Joel Brobecker wrote:
> > Are there other issues or last minute features we'd like to include
> > before we branch and/or release?
>
> i have some patches pending for using gnulib in sim ... waiting on gcc
> side to approve a top-level patch. they're not needed for up-to-date
> platforms, but to fix builds for systems like Windows that don't fully
> support current POSIX.
How are we doing on this front? If you've posted patches, would
you mind giving me URLs, so I can follow their progress?
Thank you!
--
Joel
next prev parent reply other threads:[~2021-05-24 19:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 0:04 Joel Brobecker
2021-05-10 3:20 ` Mike Frysinger via Gdb-patches
2021-05-10 22:10 ` Joel Brobecker
2021-05-24 19:40 ` Joel Brobecker [this message]
2021-05-25 2:01 ` Mike Frysinger via Gdb-patches
2021-05-26 22:03 ` Joel Brobecker
2021-05-29 15:58 ` Mike Frysinger via Gdb-patches
2021-05-10 3:52 ` Luis Machado via Gdb-patches
2021-05-10 22:11 ` Joel Brobecker
2021-05-11 11:05 ` Luis Machado via Gdb-patches
2021-05-11 17:00 ` Joel Brobecker
2021-05-12 18:15 ` Luis Machado via Gdb-patches
2021-05-24 19:42 ` Joel Brobecker
2021-05-24 20:27 ` Luis Machado via Gdb-patches
2021-05-24 21:02 ` Joel Brobecker
2021-05-25 10:46 ` Luis Machado via Gdb-patches
2021-05-26 22:04 ` Joel Brobecker
2021-05-10 5:52 ` Bernd Edlinger
2021-05-10 15:10 ` Simon Marchi via Gdb-patches
2021-05-10 16:07 ` Andrew Burgess
2021-05-10 16:57 ` Simon Marchi via Gdb-patches
2021-05-10 22:12 ` Joel Brobecker
2021-05-11 12:45 ` Rainer Orth
2021-05-11 16:57 ` Joel Brobecker
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=20210524194041.GA758326@adacore.com \
--to=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