Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Scott Linder (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: gdb-patches@sourceware.org
Subject: [review] [gdb] Support frames inlined into the outer frame
Date: Wed, 18 Mar 2020 17:10:24 -0400	[thread overview]
Message-ID: <20200318211024.57B0C2816C@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1584562651000.I8aa129c667dccc31590ffdf426586418493a6ebe@gnutoolchain-gerrit.osci.io>

Scott Linder has posted comments on this change.

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/767
......................................................................


Patch Set 1:

> Patch Set 1:
> 
> Hi Scott,
> 
> Thanks for the patch.  However, we don't really use Gerrit anymore.  We gave it a try and it didn't work so well for us, so we decided to keep the mailing list process for now.  Could you please send your patch to the gdb-patches mailing list?
> 
> Thanks!

Hi Simon,

My mistake, I haven't been following the list as closely recently. I already sent an email referencing this review to gdb-patches, so I will just reply there with the formatted patch.


-- 
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: I8aa129c667dccc31590ffdf426586418493a6ebe
Gerrit-Change-Number: 767
Gerrit-PatchSet: 1
Gerrit-Owner: Scott Linder <scott@scottlinder.com>
Gerrit-CC: Simon Marchi <simon.marchi@polymtl.ca>
Gerrit-Comment-Date: Wed, 18 Mar 2020 21:10:24 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment


  parent reply	other threads:[~2020-03-18 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 20:17 Scott Linder (Code Review)
2020-03-18 20:33 ` Simon Marchi (Code Review)
2020-03-18 21:09 ` Scott Linder (Code Review)
2020-03-18 21:10 ` Scott Linder (Code Review) [this message]
2020-03-18 21:23 ` Simon Marchi (Code Review)

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=20200318211024.57B0C2816C@gnutoolchain-gerrit.osci.io \
    --to=gerrit@gnutoolchain-gerrit.osci.io \
    --cc=gdb-patches@sourceware.org \
    --cc=gnutoolchain-gerrit@osci.io \
    /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