From: Aditya Kamath <Aditya.Kamath1@ibm.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
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 17:16:51 +0000 [thread overview]
Message-ID: <DSWPR15MB3198179A2CB1877A03660634A3D6962@DSWPR15MB319817.namprd15.prod.outlook.com> (raw)
In-Reply-To: <569e3d6c-0518-4a97-8740-63db61885ce7@polymtl.ca>
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
Hi Simon,
>Hi Aditya,
>How do you send your patch series exactly? It looks like you send each
>message separately. This results in four messages unrelated to each
>other, making it hard to follow the whole series, or to grab the full
>series with a tool like "b4".
https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceware.org_gdb_wiki_DeveloperTips-23Downloading-5Fand-5Fapplying-5Fpatches-5Ffrom-5Fthe-5Fmailing-5Flist&d=DwICaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=f-oUQ8ByG1nZ71OI9p76qywCPh7mxzU69hBYnkP9Nis&m=4rkTNUU2a8RN4d7A-qlBn6UpHX_TRYQ7KwYxbgmBw-VuBXTN5MYBhHrehbX4pT47&s=CxDjQqv61ItIbC2hFedv8-yApQgu2BJB-pVtLnQstZM&e=
>I would suggest using git-send-email to send your series. No need to
>re-send this one, but for the future.
I use git-send email only.
Here is what I do.
First git add <file>, sometime I use git add -p <file> to split my hunks.
The git commit and write my commit message.
Then git format-patch <patch_no> <commit_hash> -o <patch_directory> -“Version”
Ex: git format-patch -4 1317570d6869c3b09bea5e9a6c032195e049dcb2 -o /tls_patches/aix-thread-changes/v4/ -“v4"
Then finally I do
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.
Let me know if I need to change something.
Thanks and regards,
Aditya.
[-- Attachment #2: Type: text/html, Size: 6116 bytes --]
next prev parent reply other threads:[~2026-10-05 17:17 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 [this message]
2026-10-05 17:28 ` Aditya Kamath
2026-10-05 17:35 ` Simon Marchi
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=DSWPR15MB3198179A2CB1877A03660634A3D6962@DSWPR15MB319817.namprd15.prod.outlook.com \
--to=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=simon.marchi@polymtl.ca \
--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