From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Tomasz Jeneralczyk" <tj@schwi.pl>, <56041@debbugs.gnu.org>
Subject: [bug#56041] [PATCH v4] gnu: Add vkmark.
Date: Sun, 06 Nov 2022 09:40:14 +0000 [thread overview]
Message-ID: <CO543LB6FH92.3MPKVMBFN9Z2M@guix-framework> (raw)
In-Reply-To: <c56b4352ea644e4ffe2cbb1d20f2944366b005ff.1656343780.git.tj@schwi.pl>
Heya,
On Mon Jun 27, 2022 at 5:02 PM BST, Tomasz Jeneralczyk wrote:
> * gnu/packages/benchmark.scm (vkmark): Add variable.
"New variable.", not "Add variable."
> --- a/gnu/packages/benchmark.scm
> +++ b/gnu/packages/benchmark.scm
> @@ -645,3 +652,44 @@ (define-public sysbench
> + (revision "1"))
Use ``(revision "0")'' for the first version currently in Guix.
> + (inputs (list vulkan-loader
> + vulkan-headers
> + glm
> + assimp
> + libxcb
> + xcb-util-wm
> + wayland-protocols
> + wayland))
There should be a newline between ``inputs'' and ``(list ...)''.
> + (home-page "https://github.com/vkmark/vkmark")
home-page goes before synopsis.
-- (
next prev parent reply other threads:[~2022-11-06 9:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 15:24 [bug#56041] [PATCH] gnu: Add vkmark Tomasz Jeneralczyk
2022-06-17 19:10 ` ( via Guix-patches via
2022-06-17 19:59 ` ( via Guix-patches via
2022-06-18 8:13 ` [bug#56041] Fwd: " ( via Guix-patches via
2022-06-18 8:13 ` ( via Guix-patches via
2022-06-18 23:01 ` [bug#56041] [PATCH v2] " Tomasz Jeneralczyk
2022-06-19 8:07 ` ( via Guix-patches via
2022-06-19 9:07 ` Maxime Devos
2022-06-19 9:08 ` Maxime Devos
2022-06-19 15:46 ` [bug#56041] [PATCH v3] " Tomasz Jeneralczyk
2022-06-27 16:02 ` [bug#56041] [PATCH v4] " Tomasz Jeneralczyk
2022-11-06 9:40 ` ( via Guix-patches via [this message]
2022-11-07 15:31 ` Tomasz Jeneralczyk
2022-11-07 17:07 ` ( via Guix-patches via
2022-11-07 16:01 ` [bug#56041] [PATCH v5] " Tomasz Jeneralczyk
2022-11-07 17:09 ` ( via Guix-patches via
2023-01-08 15:11 ` bug#56041: [PATCH] " Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CO543LB6FH92.3MPKVMBFN9Z2M@guix-framework \
--to=guix-patches@gnu.org \
--cc=56041@debbugs.gnu.org \
--cc=paren@disroot.org \
--cc=tj@schwi.pl \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).