git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] chore: fix typo in .clang-format comment

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 31, 2023, 23:40 UTC
Message-ID
<xmqqbkce1hu3.fsf@gitster.g>
In-Reply-To
<ZUFQzFcgGdJsPJ8G@nand.local>
Taylor Blau <me@ttaylorr.com> writes:
Show 6 quoted lines
>> As a comment for a new contributor, it is a bit unhelpful not to
>> suggest what the "subject area" string we would use if we were
>> working on this patch, I think.
>
> Good suggestion. I would have suggested "clang-format", which is
> exactly Aditya ended up choosing, anyway. Thanks, Aditya!
Thanks.  I was being lazy when I said the above ;-)

Teaching how to fish instead of giving fish, the way I would have done is

   $ git log --no-merges --stat --full-diff .clang-format

and inspect what they use. The ones that used "clang-format:" are indeed very similar in spirit to what this one does, I would say.

Thanks.
Previous: Taylor BlauNext: Aditya Neelamraju via GitGitGadget
Message 5 of 7 in “chore: fix typo in .clang-format comment”
  1. chore: fix typo in .clang-format commentAditya Neelamraju via GitGitGadget, Oct 29, 2023
  2. Taylor BlauOct 30, 2023
  3. Junio C HamanoOct 31, 2023
  4. Taylor BlauOct 31, 2023
  5. Junio C HamanoOct 31, 2023
  6. clang-format: fix typo in commentAditya Neelamraju via GitGitGadget, Oct 31, 2023
  7. Taylor BlauOct 31, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.