From: phodina via Guix-patches via <guix-patches@gnu.org>
To: Raghav Gururajan <rg@raghavgururajan.name>
Cc: 50283@debbugs.gnu.org
Subject: [bug#50283] [PATCH v3 2/2] gnu: Add hwinfo.
Date: Tue, 31 Aug 2021 11:18:59 +0000 [thread overview]
Message-ID: <Sv4MDv5eLZBT7eCXsZgrOkx1PakFEtMDhUD4ull4T1gFy2y6bR8UIw00BhVqciqzr_78Rd3DZ0_k5tq-bbrhy4DwFHSp-Q0XeGXurt_dXgg=@protonmail.com> (raw)
In-Reply-To: <20210830233353.19811-2-rg@raghavgururajan.name>
Hi Raghav,
thanks for the patches!
Just what about hw-probe package? Should I create a new version of the patch?
PH
next prev parent reply other threads:[~2021-08-31 11:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 19:31 [bug#50283] HwInfo Raghav Gururajan via Guix-patches via
2021-08-30 19:35 ` [bug#50283] [PATCH v1 1/2] gnu: Add libx86emu Raghav Gururajan via Guix-patches via
2021-08-30 19:35 ` [bug#50283] [PATCH v1 2/2] gnu: Add hwinfo Raghav Gururajan via Guix-patches via
2021-08-30 23:13 ` [bug#50283] [PATCH v1 1/2] gnu: Add libx86emu pelzflorian (Florian Pelz)
2021-08-30 23:27 ` [bug#50283] HwInfo Raghav Gururajan via Guix-patches via
2021-08-31 9:35 ` pelzflorian (Florian Pelz)
2021-08-31 9:41 ` pelzflorian (Florian Pelz)
2021-08-31 9:48 ` pelzflorian (Florian Pelz)
2021-08-30 22:27 ` [bug#50283] [PATCH v2 1/2] gnu: Add libx86emu Raghav Gururajan via Guix-patches via
2021-08-30 22:27 ` [bug#50283] [PATCH v2 2/2] gnu: Add hwinfo Raghav Gururajan via Guix-patches via
2021-08-30 23:33 ` [bug#50283] [PATCH v3 1/2] gnu: Add libx86emu Raghav Gururajan via Guix-patches via
2021-08-30 23:33 ` [bug#50283] [PATCH v3 2/2] gnu: Add hwinfo Raghav Gururajan via Guix-patches via
2021-08-31 11:18 ` phodina via Guix-patches via [this message]
2021-09-01 1:28 ` Raghav Gururajan via Guix-patches via
2021-09-18 12:59 ` [bug#50283] Patch status phodina via Guix-patches via
2021-10-01 23:30 ` [bug#50283] HwInfo Raghav Gururajan via Guix-patches via
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='Sv4MDv5eLZBT7eCXsZgrOkx1PakFEtMDhUD4ull4T1gFy2y6bR8UIw00BhVqciqzr_78Rd3DZ0_k5tq-bbrhy4DwFHSp-Q0XeGXurt_dXgg=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=50283@debbugs.gnu.org \
--cc=phodina@protonmail.com \
--cc=rg@raghavgururajan.name \
/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.