all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 41778@debbugs.gnu.org
Subject: [bug#41778] [PATCH 0/3] Add ppsspp
Date: Tue, 30 Jun 2020 00:02:36 +0200	[thread overview]
Message-ID: <87wo3pil8j.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <0e2c18a84e232f73a72d755a692feaece0118396.camel@student.tugraz.at> (Leo Prikler's message of "Mon, 29 Jun 2020 12:02:18 +0200")

Hello,

Leo Prikler <leo.prikler@student.tugraz.at> writes:

> Following the release of version 1.10, I've updated my package
> descriptions.  I've also been able to unbundle some sources, but not
> all of them.

OOC, did you try to symlink sources instead of copying them?

Note that you don't mention what is left to unbundle. Would it make
sense to add this information?

Otherwise, LGTM, barring the description of spirv-cross, where I suggest
to drop the "NOTE:" part. It reminds me taisei package felt through the
cracks. I'll apply it once spirv-cross is pushed.

Regards,
-- 
Nicolas Goaziou




  parent reply	other threads:[~2020-06-29 22:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 21:40 [bug#41778] [PATCH WIP 0/2] Add ppsspp Leo Prikler
2020-06-09 21:47 ` [bug#41778] [PATCH 1/2] gnu: Add armips Leo Prikler
2020-06-09 21:47   ` [bug#41778] [PATCH 2/2] gnu: Add ppsspp Leo Prikler
2020-06-29 10:02 ` [bug#41778] [PATCH 0/3] " Leo Prikler
2020-06-29 10:06   ` [bug#41778] [PATCH 1/3] gnu: Add armips Leo Prikler
2020-06-29 10:06   ` [bug#41778] [PATCH 2/3] gnu: add spirv-cross Leo Prikler
2020-06-29 10:06   ` [bug#41778] [PATCH 3/3] gnu: Add ppsspp Leo Prikler
2020-06-29 22:02   ` Nicolas Goaziou [this message]
2020-06-29 23:33     ` [bug#41778] [PATCH 0/3] " Leo Prikler
2020-06-30 15:08       ` bug#41778: " Nicolas Goaziou
2020-06-30 21:31         ` [bug#41778] " Leo Prikler
2020-07-01 10:15           ` Nicolas Goaziou

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=87wo3pil8j.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=41778@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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.