all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: 39762-done@debbugs.gnu.org
Cc: cpuid@etallen.com
Subject: bug#39762: [PATCH] gnu: cpuid: Update to 20200211.
Date: Mon, 24 Feb 2020 00:49:52 +0100	[thread overview]
Message-ID: <877e0cuan3.fsf@nckx> (raw)
In-Reply-To: <CAEwRq=qNXOz0Fs=D=PhfBCeyzrzO2Np3ccibYnir8yRcOCdazA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]

Vincent,

Thanks for the update!  I only recently (this year?) learnt of 
this readable alternative to /proc/cpuinfo.  Glad to hear it's 
seeing more action.

Vincent Legoll 写道:
> But in normal mode, output changed a lot, some separators 
> changed from ":"
> to "="

This was deliberate, for consistency:

  Wed Feb  5 2020 Todd Allen <todd.allen@etallen.com>
    * cpuid.c: Changed mp_synth fields to use '=' separator 
    instead of ':',
      like every other value.
    * cpuid.c: Changed processor serial number to use '=' 
    separator instead
      of ':', like every other value.

> a lot of reported values, new things... This will probably break
> any simplistic parsing of that output, if there is anything 
> doing that in
> guix...

No:

  ~ λ guix refresh -l cpuid
  No dependents other than itself: cpuid@20200116

It's possible there's something out there calling cpuid from 
$PATH, but…

> Guixers, please advise how to proceed further.

…honestly, you're overthinking it. :-)  There's a time to be 
cautious but bumping cpuid is probably not it.

Guix is exceptionally good at installing previous versions of 
packages for those who disagree.  I've pushed your patch as 
08fee94d0fd96ea2b40f9fec80dc3fa19e283019.

> Subject: [PATCH] gnu: cpuid: Update to 20200211. * 
> gnu/packages/linux.scm
> (cpuid): Update to 20200211.

Note that git expects an empty line (newline) between the commit 
summary and the body of the message:

  gnu: cpuid: Update to 20200211.

  * gnu/packages/linux.scm (cpuid): Update to 20200211.

Thanks again,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2020-02-23 23:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23 22:54 [bug#39762] [PATCH] gnu: cpuid: Update to 20200211 Vincent Legoll
2020-02-23 23:49 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-02-24 15:12 ` Todd Allen
2020-02-24 19:14   ` Vincent Legoll

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=877e0cuan3.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=39762-done@debbugs.gnu.org \
    --cc=cpuid@etallen.com \
    --cc=me@tobias.gr \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.