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, 01:21 UTC
Message-ID
<xmqqsfiao47q.fsf@gitster.g>
In-Reply-To
<CAPig+cQ6_7wf6C280Rqi7mcTCiQp-n5GiLWTPazfcUcGFeZi0g@mail.gmail.com>
Eric Sunshine <sunshine@sunshineco.com> writes:
Show 10 quoted lines
> Makes sense. Well explained.
>
> A separate problem is that chainlint.pl doesn't fall back to a
> sensible non-zero value if ncores() returns 0 (or some other nonsense
> value). That is, of course, outside the scope of the well-focused
> problem fix which this standalone patch addresses. I may end up
> submitting a fix separately to make it fall back sensibly.
> ...
> As mentioned elsewhere[1], this code may eventually be dropped
> altogether, but this fix is good to have in the meantime. Thanks.
Thanks, both.  Will apply.
Previous: Eric SunshineNext: Andreas Hasenack
Message 3 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.