From: Simon Marchi <simark@simark.ca>
To: scott@scottlinder.com, Gdb Patches <gdb-patches@sourceware.org>
Subject: Re: [RFC][PATCH] Support frames inlined into the outer frame
Date: Wed, 18 Mar 2020 17:27:24 -0400 [thread overview]
Message-ID: <94abc873-ed9f-e469-5e5d-56b66ecb847a@simark.ca> (raw)
In-Reply-To: <c0d1c2108051628b86cca49df9380035@scottlinder.com>
On 2020-03-18 5:17 p.m., scott@scottlinder.com wrote:
> It was pointed out that posting patches directly to the list is
> preferred over Gerrit, so I abandoned the Gerrit review and I'm
> attaching the patch here. The wiki says a git-format-patch'd attachment
> is OK, but let me know if it isn't the norm!
Hi Scott,
Doing git-format-patch and attaching the patch is fine, since it pretty much
ensures the patch is not mangled by your email client. But really the preferred
way is to use "git-send-email". This sends the content of the patch in the body
of the email, so it makes it easier to reply, quoting parts of the patch. It also
makes it easy to send multiple patches in series.
Simon
next prev parent reply other threads:[~2020-03-18 21:27 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 [this message]
2020-03-18 21:42 ` scott
2020-03-18 21:45 ` Simon Marchi
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=94abc873-ed9f-e469-5e5d-56b66ecb847a@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