public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Lancelot SIX <lsix@lancelotsix.com>
To: Bruno Larsen <blarsen@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: add 'maintenance print record-instruction' command
Date: Thu, 8 Dec 2022 09:32:12 +0000	[thread overview]
Message-ID: <20221208093212.ezujirvp4nbdth3r@ubuntu.lan> (raw)
In-Reply-To: <ec911832-7d0e-cc6d-7159-17e7b1a08bf9@redhat.com>

> None maintenance_print functions end with _command, so I don't think it is a
> hard rule, but if you think I should add it, I can do it.

Indeed, maintenance commands do not have seem to have this prefix, so
you should leave it as it is.  My bad.

Best,
Lancelot.

> 
> I agree with everything else you said, it'll all be fixed in v2.
> 
> -- 
> Cheers,
> Bruno
> 

  reply	other threads:[~2022-12-08  9:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 13:50 Bruno Larsen
2022-12-07 14:37 ` Lancelot SIX
2022-12-08  8:45   ` Bruno Larsen
2022-12-08  9:32     ` Lancelot SIX [this message]
2022-12-15 21:27   ` Tom Tromey
2022-12-15 21:29 ` Tom Tromey

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=20221208093212.ezujirvp4nbdth3r@ubuntu.lan \
    --to=lsix@lancelotsix.com \
    --cc=blarsen@redhat.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).