From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 0/3] Suppressing CLI notifications
Date: Fri, 14 Jan 2022 12:13:12 +0000 [thread overview]
Message-ID: <DM6PR11MB3884E535EBD95075F227E8D3C4549@DM6PR11MB3884.namprd11.prod.outlook.com> (raw)
In-Reply-To: <cover.1638370938.git.tankut.baris.aktemur@intel.com>
On Wednesday, December 1, 2021 4:08 PM, Aktemur, Tankut Baris wrote:
>
> Hello,
>
> This is a small series about suppressing CLI notifications. This can
> be useful for scripts.
>
> Regards
> Baris
>
> Tankut Baris Aktemur (3):
> gdb/cli: convert cli_suppress_notification from int to bool
> gdb/cli: add a 'normal_stop' option to 'cli_suppress_notification'
> gdb: add the 'set/show suppress-notification-cli' command
>
Kindly pinging.
Thanks
-Baris
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2022-01-14 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 15:08 Tankut Baris Aktemur
2021-12-01 15:08 ` [PATCH 1/3] gdb/cli: convert cli_suppress_notification from int to bool Tankut Baris Aktemur
2022-01-14 15:52 ` Tom Tromey
2021-12-01 15:08 ` [PATCH 2/3] gdb/cli: add a 'normal_stop' option to 'cli_suppress_notification' Tankut Baris Aktemur
2022-01-14 16:01 ` Tom Tromey
2021-12-01 15:08 ` [PATCH 3/3] gdb: add the 'set/show suppress-notification-cli' command Tankut Baris Aktemur
2022-01-14 16:04 ` Tom Tromey
2022-01-18 10:41 ` Andrew Burgess
2022-01-14 12:13 ` Aktemur, Tankut Baris [this message]
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=DM6PR11MB3884E535EBD95075F227E8D3C4549@DM6PR11MB3884.namprd11.prod.outlook.com \
--to=tankut.baris.aktemur@intel.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).