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

Re: [PATCH] chainlint.pl: fix /proc/cpuinfo regexp

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 23, 2022, 23:53 UTC
Message-ID
<xmqqfse9mdm2.fsf@gitster.g>
In-Reply-To
<CANYNYEETCaaQGOXVLrRCC8wdS-uD66BHqr98Eetb+1GVk5WkTg@mail.gmail.com>
Andreas Hasenack <andreas@canonical.com> writes:
> Should I still change the commit message regarding where I mention the
> commit that introduced this, as explained by Eric? From the activity I
> saw overnight it looks like things were already picked up and it
> doesn't matter anymore.

Sorry, I should have said "will apply with tweaked log message" to reduce the need for a round-trip. Please double check what is queued in 'seen' and send in replacements before it gets merged down to 'next' if there are still things you may want to update. If you are happy with what is in 'seen', no further action is needed at least for now.

Thanks.
Previous: Eric Sunshine
Message 6 of 6 in “chainlint.pl: fix /proc/cpuinfo regexp”
  1. chainlint.pl: fix /proc/cpuinfo regexpAndreas Hasenack via GitGitGadget, Nov 22, 2022
  2. Eric SunshineNov 22, 2022
  3. Junio C HamanoNov 23, 2022
  4. Andreas HasenackNov 23, 2022
  5. Eric SunshineNov 23, 2022
  6. Junio C HamanoNov 23, 2022

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.