public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Enze Li <enze.li@hotmail.com>, gdb-patches@sourceware.org
Cc: enze.li@gmx.com
Subject: Re: [PATCH] gdb: remove gdb_indent.sh
Date: Wed, 1 Feb 2023 11:26:53 -0500	[thread overview]
Message-ID: <c853ca76-6e9b-5725-7107-679fa653eba0@simark.ca> (raw)
In-Reply-To: <OS3P286MB2152EEC03912301D0BA5F7DEF0D19@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM>



On 2/1/23 09:37, Enze Li via Gdb-patches wrote:
> GDB has been converted to a C++ program for many years[1], and the
> gdb_indent.sh will not be used any more. Therefore, remove the script as
> obvious.

FWIW, I think this is ok.  It seems irrelevant today.

Simon

  reply	other threads:[~2023-02-01 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 14:37 Enze Li
2023-02-01 16:26 ` Simon Marchi [this message]
2023-02-02 13:01   ` Enze Li

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=c853ca76-6e9b-5725-7107-679fa653eba0@simark.ca \
    --to=simark@simark.ca \
    --cc=enze.li@gmx.com \
    --cc=enze.li@hotmail.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).