From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: <56041@debbugs.gnu.org>
Subject: [bug#56041] Fwd: Re: [bug#56041] [PATCH] gnu: Add vkmark.
Date: Sat, 18 Jun 2022 09:13:06 +0100 [thread overview]
Message-ID: <CKT3Y2DYV376.2UXGJ8F3Z554J@guix-aspire> (raw)
In-Reply-To: <b9edc90fb6081f2ea0495b9c22527134@schwi.pl>
Forwarded message from Tomasz Jeneralczyk on Fri Jun 17, 2022 at 10:40 PM:
On 2022-06-17 19:10, ( wrote:
> On Fri Jun 17, 2022 at 4:24 PM BST, Tomasz Jeneralczyk wrote:
> I think it's common to include an explanation of why tags aren't used
> :)
The only tag in the repo is "2017.08" and it's a bit old considering
the latest commit was just a few days ago. I did not manage to compile
the old version successfully anyway, I suspect the api of the libraries
it uses has changed significantly in the meantime.
On the latest commit all benchmark suites run just fine for me on xcb
backend,
and someone on irc confirmed it works on wayland too so I rolled with
that.
Do you want me to write a comment there explaining why I used a specific
commit?
> Nitpick: file-name usually comes after uri in most of the packages I've
> seen. Maybe run guix style, if you haven't already.
All I can tell is guix style does not do much, could not even fix this
simple
issue.
> Why include cmake? It seems to compile without it :)
You are right. I think it is there because during building process it
spits
out "Found CMAKE: NO" during compilation and I thought that was an
issue.
> Maybe expand this to "Extensible benchmarking suite for Vulkan" or
> something? I'd say this synopsis is a bit too short.
your suggestion sounds good.
So do I send a new patch in this thread (with the same or a different
subject?) or make a new thread with it?
Please only send plain-text email; see <https://useplaintext.email>. Thanks!
next prev parent reply other threads:[~2022-06-18 8:15 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 ` ( via Guix-patches via [this message]
2022-06-18 8:13 ` [bug#56041] Fwd: " ( 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CKT3Y2DYV376.2UXGJ8F3Z554J@guix-aspire \
--to=guix-patches@gnu.org \
--cc=56041@debbugs.gnu.org \
--cc=paren@disroot.org \
/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.