From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [branching soon!] GDB 13 release -- 2022-12-04 update
Date: Mon, 05 Dec 2022 13:43:50 -0700 [thread overview]
Message-ID: <87lenlk2d5.fsf@tromey.com> (raw)
In-Reply-To: <Y41jL16V84Ok1kx3@adacore.com> (Joel Brobecker via Gdb-patches's message of "Mon, 5 Dec 2022 07:19:11 +0400")
>>>>> "Joel" == Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org> writes:
Joel> What do you think of the following approach? Disable Windows target-async
Joel> for now, until you have a fix. That way, when I branch, it's all set,
Joel> and I can follow the standard procedure for generating the first
Joel> pre-release. Then, when we have the fix for the interrupt issue, we can
Joel> re-enable it, with the option of backporting it to the GDB 13 branch
Joel> if OK to do so.
I found a fix today, so let's try that unless the fix looks like trouble.
If we don't want that fix, it's easy to disable async, that's a simple
patch, so I can easily do it later this week.
Tom
next prev parent reply other threads:[~2022-12-05 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 4:33 Joel Brobecker
2022-12-04 15:45 ` Tom Tromey
2022-12-05 3:19 ` Joel Brobecker
2022-12-05 20:43 ` Tom Tromey [this message]
2022-12-06 5:25 ` Joel Brobecker
2022-12-09 11:14 ` Luis Machado
2022-12-09 12:30 ` Eli Zaretskii
2022-12-09 13:23 ` Joel Brobecker
2022-12-09 14:54 ` Eli Zaretskii
2022-12-09 15:03 ` 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=87lenlk2d5.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).