From: Eli Zaretskii <eliz@gnu.org>
To: Sergio Durigan Junior <sergiodj@sergiodj.net>
Cc: gdb-patches@sourceware.org, simon.marchi@polymtl.ca,
doko@debian.org, mjeanson@debian.org
Subject: Re: [PATCH] Remove support for the Common Trace Format (CTF)
Date: Sun, 10 May 2026 07:47:17 +0300 [thread overview]
Message-ID: <86qznj3m7e.fsf@gnu.org> (raw)
In-Reply-To: <20260510022813.2221582-1-sergiodj@sergiodj.net> (message from Sergio Durigan Junior on Sat, 9 May 2026 22:28:13 -0400)
> From: Sergio Durigan Junior <sergiodj@sergiodj.net>
> Cc: Simon Marchi <simon.marchi@polymtl.ca>, doko@debian.org,
> Michael Jeanson <mjeanson@debian.org>,
> Sergio Durigan Junior <sergiodj@sergiodj.net>
> Date: Sat, 9 May 2026 22:28:13 -0400
>
> gdb/Makefile.in | 10 +-
> gdb/NEWS | 22 +-
> gdb/configure.ac | 43 -
> gdb/doc/gdb.texinfo | 48 +-
> gdb/mi/mi-main.c | 12 +-
> gdb/testsuite/gdb.base/completion.exp | 10 -
> gdb/testsuite/gdb.trace/actions.exp | 22 -
> .../gdb.trace/mi-trace-frame-collected.exp | 23 -
> .../gdb.trace/mi-trace-unavailable.exp | 23 -
> gdb/testsuite/gdb.trace/report.exp | 14 -
> gdb/testsuite/gdb.trace/tstatus.exp | 14 -
> gdb/testsuite/gdb.trace/tsv.exp | 12 -
> gdb/testsuite/gdb.trace/unavailable.exp | 22 -
> gdb/testsuite/gdb.trace/while-stepping.exp | 22 -
> gdb/top.c | 10 -
> gdb/tracectf.c | 1728 -----------------
> gdb/tracectf.h | 25 -
> gdb/tracefile.c | 25 +-
> gdb/tracepoint.h | 2 -
> 19 files changed, 31 insertions(+), 2056 deletions(-)
> delete mode 100644 gdb/tracectf.c
> delete mode 100644 gdb/tracectf.h
Thanks, the documentation parts are okay.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2026-05-10 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 2:28 Sergio Durigan Junior
2026-05-10 4:47 ` Eli Zaretskii [this message]
2026-05-10 12:43 ` Simon Marchi
2026-05-10 16:42 ` Sergio Durigan Junior
2026-05-11 1:25 ` Simon Marchi
2026-05-11 3:52 ` Sergio Durigan Junior
2026-05-11 3:56 ` Sergio Durigan Junior
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=86qznj3m7e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=doko@debian.org \
--cc=gdb-patches@sourceware.org \
--cc=mjeanson@debian.org \
--cc=sergiodj@sergiodj.net \
--cc=simon.marchi@polymtl.ca \
/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