From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4] Add .clang-format
Date: Mon, 06 Oct 2025 12:42:00 -0600 [thread overview]
Message-ID: <87ms633m9z.fsf@tromey.com> (raw)
In-Reply-To: <20251006183901.1239002-1-tom@tromey.com> (Tom Tromey's message of "Mon, 6 Oct 2025 12:38:59 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> +# * gettext calls like "_()" are reformatted to "_ ()"
Tom> +# I don't think there's an upstream bug for this yet
I found a pull request for this, so I'll be updating the comment
locally. I don't plan to re-send just for this.
Tom
next prev parent reply other threads:[~2025-10-06 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 18:38 Tom Tromey
2025-10-06 18:42 ` Tom Tromey [this message]
2025-10-06 18:46 ` Andrew Pinski
2025-10-06 19:39 ` Tom Tromey
2025-10-08 22:24 ` Simon Marchi
2025-10-13 6:59 ` Jason Merrill
2025-12-10 19:22 ` Tom Tromey
2025-10-11 22:49 ` Kevin Buettner
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=87ms633m9z.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/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