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

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

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Nov 23, 2022, 15:52 UTC
Message-ID
<CAPig+cSVjnrHEZxosbS1Au7LRbDRZt_r9dr78S37FPXdb3W2QA@mail.gmail.com>
In-Reply-To
<CANYNYEETCaaQGOXVLrRCC8wdS-uD66BHqr98Eetb+1GVk5WkTg@mail.gmail.com>
On Wed, Nov 23, 2022 at 7:17 AM Andreas Hasenack <andreas@canonical.com> wrote:
> 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.

No need to resend. Junio tweaked the commit message[1] when he picked up the patch.

[1]: https://github.com/git/git/commit/1f51b77f4f3f4d05f249f80713b2969e4069c109
Previous: Andreas HasenackNext: Junio C Hamano
Message 5 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.