From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 12 preparation -- 2022-03-06 update
Date: Mon, 7 Mar 2022 20:14:04 +0400 [thread overview]
Message-ID: <YiYvTNCKkjEzam7+@adacore.com> (raw)
In-Reply-To: <87bkyhrel6.fsf@tromey.com>
Hi Tom,
> Joel> Added Since the Last Update:
> Joel> ----------------------------
> Joel> <none>
>
> I'd like to add the --dbx deprecation patch.
>
> https://sourceware.org/pipermail/gdb-patches/2022-March/186306.html
>
> I sent a note to the main gdb list. I suppose we could simply check it
> in now and back it out before 12 if there are strong objections. WDYT?
No problem with me. I doubt anyone will object, so I vote for
adding the deprecation note now. Like you say, if there are
objections, it's really easy to back out.
--
Joel
next prev parent reply other threads:[~2022-03-07 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 10:15 Joel Brobecker
2022-03-07 8:50 ` Luis Machado
2022-03-07 11:45 ` Joel Brobecker
2022-03-07 15:01 ` Tom Tromey
2022-03-07 16:14 ` Joel Brobecker [this message]
2022-03-07 17:43 ` Tom Tromey
2022-03-07 15:15 ` Andrew Burgess
2022-03-07 16:14 ` 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=YiYvTNCKkjEzam7+@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).