Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3 0/2] Have ptype support hex display of offsets and sizes
Date: Sun, 25 Apr 2021 18:12:26 +0100	[thread overview]
Message-ID: <20210425171215.cqqzfyxhmcda35up@Plymouth> (raw)
In-Reply-To: <871razg0k4.fsf@tromey.com>

Hi,

I just pushed those 2 patches to master.

Thanks.

Lancelot.

On Sat, Apr 24, 2021 at 09:32:59AM -0600, Tom Tromey wrote:
> >>>>> "Lancelot" == Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
> Lancelot> Hi,
> Lancelot> Here is a updated version of the series.  The first patch is unchanged
> Lancelot> from previous submission.  Documentation and code style have been
> Lancelot> updated in the second patch of the series according to reviews.
> Lancelot> The second patch has also been updated to handle conflicts in
> Lancelot> gdb/testsuite/gdb.base/ptype-offsets.exp after the following patch
> Lancelot> landed in master: https://sourceware.org/pipermail/gdb-patches/2021-April/178016.html.
> 
> Thank you for doing this.  This is ok to commit.
> 
> Tom

      reply	other threads:[~2021-04-25 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 22:28 Lancelot SIX via Gdb-patches
2021-04-23 22:28 ` [PATCH v3 1/2] typeprint.h: reorder struct declaration Lancelot SIX via Gdb-patches
2021-04-23 22:28 ` [PATCH v3 2/2] [PR gdb/22640] ptype: add option to use hexadecimal notation Lancelot SIX via Gdb-patches
2021-04-24  6:15   ` Eli Zaretskii via Gdb-patches
2021-04-24 15:32 ` [PATCH v3 0/2] Have ptype support hex display of offsets and sizes Tom Tromey
2021-04-25 17:12   ` Lancelot SIX via Gdb-patches [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=20210425171215.cqqzfyxhmcda35up@Plymouth \
    --to=gdb-patches@sourceware.org \
    --cc=lsix@lancelotsix.com \
    --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