From: Simon Marchi <simark@simark.ca>
To: scott@scottlinder.com
Cc: Gdb Patches <gdb-patches@sourceware.org>
Subject: Re: [RFC][PATCH] Support frames inlined into the outer frame
Date: Wed, 18 Mar 2020 17:45:36 -0400 [thread overview]
Message-ID: <09367f43-a9a5-cfb1-f854-8084653f0c70@simark.ca> (raw)
In-Reply-To: <45b7adaa80fd9f1fc2598ea204273674@scottlinder.com>
On 2020-03-18 5:42 p.m., scott@scottlinder.com wrote:
> Hi Simon,
>
> Makes sense, I'll use git-send-email in the future. Thank you for
> bearing with
> me as I get set up, and I'm sorry for the spam. I also just noticed I
> neglected
> to delete Gerrit's Change-Id from the commit message, so I may send an
> updated
> diff with git-send-email once I have it set up, as a bit of a smoke
> test.
>
> Scott
No worries, I'm happy to help people get the right tools, it helps everybody
in the long run. Don't sweat about Gerrit's change id. In fact, we might
even try to use it in the future to track patch versions on Patchwork (we
are supposed to get an instance running soon).
next prev parent reply other threads:[~2020-03-18 21:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 20:43 scott
2020-03-18 21:17 ` scott
2020-03-18 21:27 ` Simon Marchi
2020-03-18 21:42 ` scott
2020-03-18 21:45 ` Simon Marchi [this message]
2020-03-18 22:06 ` Scott Linder
2020-03-18 22:11 ` [PATCH] [gdb] " Scott Linder
2020-03-24 10:22 ` Andrew Burgess
2020-03-30 22:22 ` scott
2020-03-31 19:18 ` [PATCH v2] " Scott Linder
2020-04-03 17:00 ` Andrew Burgess
2020-04-17 20:41 ` Scott Linder
2020-04-03 19:37 ` Luis Machado
2020-04-17 20:51 ` Scott Linder
2020-06-04 16:11 ` Simon Marchi
2020-06-04 19:23 ` Simon Marchi
2020-06-08 12:00 ` Luis Machado
2020-06-08 16:01 ` Simon Marchi
2020-06-08 16:10 ` Luis Machado
2020-04-02 19:30 ` [PATCH] " Pedro Alves
2020-04-17 20:35 ` Scott Linder
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=09367f43-a9a5-cfb1-f854-8084653f0c70@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=scott@scottlinder.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