From: Simon Marchi <simon.marchi@polymtl.ca>
To: Aditya Kamath <Aditya.Kamath1@ibm.com>,
Aditya Vidyadhar Kamath <akamath996@gmail.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
"tom@tromey.com" <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
SANGAMESH MALLAYYA <sangamesh.swamy@in.ibm.com>
Subject: Re: [PATCH v4 1/4] Fix styles in aix-thread.c to follow GNU style code.
Date: Mon, 5 Oct 2026 13:35:50 -0400 [thread overview]
Message-ID: <7fd73ac2-86f4-4c9f-9087-c5a307f54933@polymtl.ca> (raw)
In-Reply-To: <DSWPR15MB319817A5270B206D6AC1453406D6962@DSWPR15MB319817.namprd15.prod.outlook.com>
On 10/5/26 1:28 PM, Aditya Kamath wrote:
> Hi Simon,
>
>>git send-email --to=ulrich.weigand@de.ibm.com --to=simon.marchi@polymtl.ca >--to=tom@tromey.com --cc=gdb-patches@sourceware.org —>cc=Aditya.Kamath1@ibm.com --cc=sangamesh.swamy@in.ibm.com v4-0005->Fix-32-bit-GPR-and-SPR-register-reads-writes-in-pthd.patch
>
>
>
>>One by one I send using 4 commands.
>
>
> From the link you shared, I realized that the expected workflow is:
>
> git am -3 <patch files...>
>
> which means I should send the entire patch series using a single
>
> git send-email invocation rather than sending each patch separately.
>
> Thanks for pointing me to that documentation.
>
> I'll do that for future patch series.
Exactly, if you want to send the top 4 commits as one series, you can do
something like:
$ git send-email HEAD~4 ...
All 4 messages will be linked together people's mail inbox (if they have
enabled threading) and on the web archives.
Simon
next prev parent reply other threads:[~2026-10-05 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 11:44 Aditya Vidyadhar Kamath
2026-10-05 14:06 ` Simon Marchi
2026-10-05 17:16 ` Aditya Kamath
2026-10-05 17:28 ` Aditya Kamath
2026-10-05 17:35 ` Simon Marchi [this message]
2026-10-05 14:19 ` Simon Marchi
2026-10-05 18:54 ` Aditya Kamath
2026-10-05 20:06 ` Simon Marchi
2026-10-06 13:23 ` Aditya Kamath
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=7fd73ac2-86f4-4c9f-9087-c5a307f54933@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=Aditya.Kamath1@ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=akamath996@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sangamesh.swamy@in.ibm.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