From: Simon Marchi <simon.marchi@polymtl.ca>
To: Aditya Vidyadhar Kamath <akamath996@gmail.com>,
ulrich.weigand@de.ibm.com, tom@tromey.com
Cc: gdb-patches@sourceware.org, Aditya.Kamath1@ibm.com,
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 10:06:22 -0400 [thread overview]
Message-ID: <569e3d6c-0518-4a97-8740-63db61885ce7@polymtl.ca> (raw)
In-Reply-To: <20261005114435.31454-2-akamath996@gmail.com>
On 10/5/26 7:44 AM, Aditya Vidyadhar Kamath wrote:
> From: Aditya Vidyadhar Kamath <aditya.kamath1@ibm.com>
>
> https://sourceware.org/gdb/wiki/Internals%20GDB-C-Coding-Standards
> As per GDB code guidelines making minor changes to follow before
> cleaning up aix-thread.c legacy code.
>
> The following things were done:
>
> 1: 80 length column maintained now.
> 2: Some functions changed from function() to function ()
> 3: Switch case also changed [only style] to follow the guideline.
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://sourceware.org/gdb/wiki/DeveloperTips#Downloading_and_applying_patches_from_the_mailing_list
I would suggest using git-send-email to send your series. No need to
re-send this one, but for the future.
Simon
next prev parent reply other threads:[~2026-10-05 14:06 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 [this message]
2026-10-05 17:16 ` Aditya Kamath
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=569e3d6c-0518-4a97-8740-63db61885ce7@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=Aditya.Kamath1@ibm.com \
--cc=akamath996@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sangamesh.swamy@in.ibm.com \
--cc=tom@tromey.com \
--cc=ulrich.weigand@de.ibm.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