From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb] Fix end-of-comment formatting
Date: Sun, 20 Sep 2026 22:17:25 -0400 [thread overview]
Message-ID: <ff0ef5c7-dd44-41f8-af7a-fe1a800ba3be@simark.ca> (raw)
In-Reply-To: <20260920212359.712032-1-tdevries@suse.de>
On 2026-09-20 17:23, Tom de Vries wrote:
> I came across a comment ending in '. */' with three instead of two spaces.
>
> Fix this using:
> ...
> $ find gdb* -type f -name "*.cc" -o -name "*.c" -o -name "*.h" \
> | xargs sed -i 's%\([^ \t]\)\. *\*/%\1. */%'
> ...
> and manually reverting two changes for "loc. byte seq.".
You are authorized to commit these as obvious :)
Simon
next prev parent reply other threads:[~2026-09-21 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 21:23 Tom de Vries
2026-09-21 2:17 ` Simon Marchi [this message]
2026-09-21 7:45 ` Tom de Vries
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=ff0ef5c7-dd44-41f8-af7a-fe1a800ba3be@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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