public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Enze Li <lienze2010@hotmail.com>
Cc: pedro@palves.net, tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v8 2/3] gdb/doc: Documentation for the new print command
Date: Sat, 23 Apr 2022 12:20:08 +0300	[thread overview]
Message-ID: <835yn0p35j.fsf@gnu.org> (raw)
In-Reply-To: <MEAP282MB029309CDBB1C7DBF06A0152EDDF69@MEAP282MB0293.AUSP282.PROD.OUTLOOK.COM> (message from Enze Li via Gdb-patches on Sat, 23 Apr 2022 17:15:57 +0800)

> Date: Sat, 23 Apr 2022 17:15:57 +0800
> From: Enze Li via Gdb-patches <gdb-patches@sourceware.org>
> Cc: gdb-patches@sourceware.org
> 
> Document the new command "print nibbles" and add a NEWS entry.
> ---
>  gdb/NEWS            |  5 +++++
>  gdb/doc/gdb.texinfo | 35 +++++++++++++++++++++++++++++++----
>  2 files changed, 36 insertions(+), 4 deletions(-)

This is OK, thanks.

  reply	other threads:[~2022-04-23  9:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23  9:12 [PING][PATCH v8 0/3] gdb: Add new 'print nibbles' feature Enze Li
2022-04-23  9:14 ` [PATCH v8 1/3] " Enze Li
2022-04-23  9:15 ` [PATCH v8 2/3] gdb/doc: Documentation for the new print command Enze Li
2022-04-23  9:20   ` Eli Zaretskii [this message]
2022-04-23  9:16 ` [PATCH v8 3/3] gdb/python: Export nibbles to python layer Enze Li
2022-04-23  9:22   ` Eli Zaretskii
2022-06-07 13:44     ` Enze Li
2022-06-07 13:44     ` Enze Li
2022-06-06 13:41 ` [PING][PATCH v8 0/3] gdb: Add new 'print nibbles' feature Tom Tromey
2022-06-07 13:29   ` Enze Li
2022-06-18  3:29 ` Enze Li
     [not found] <20220416175963.3211-1-lienze2010@hotmail.com>
     [not found] ` <20220416181725.7176-1-lienze2010@hotmail.com>
2022-04-16 18:17   ` [PATCH v8 2/3] gdb/doc: Documentation for the new print command 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=835yn0p35j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=lienze2010@hotmail.com \
    --cc=pedro@palves.net \
    --cc=tom@tromey.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).