From: jgart via Guix-patches via <guix-patches@gnu.org>
To: "Leo Prikler" <leo.prikler@student.tugraz.at>, 47887@debbugs.gnu.org
Cc: Raghav Gururajan <rg@raghavgururajan.name>,
jackhill@jackhill.us, rprior@protonmail.com, ccao001@fiu.edu
Subject: [bug#47887] [PATCH 1/2] gnu: Add gnome-2048
Date: Mon, 19 Apr 2021 20:28:45 +0000 [thread overview]
Message-ID: <5e0a62414eff577fdbc26a73ee0e553c@dismail.de> (raw)
In-Reply-To: <bf6762d8daee52c0ab7d7dccc7a6d4cabede6ab5.camel@student.tugraz.at>
> Please make sure to stay within our very tight margins next time ;)
I think that must have been Carla abusing the description field string as if it were a zettelkasten think space (via leafpad editor) in a guix environment.
We'll be more careful next time :)
Thanks for merging Leo!
all the best,
jgart
April 19, 2021 5:54 AM, "Leo Prikler" <leo.prikler@student.tugraz.at> wrote:
> Hi jgart,
>
> Am Montag, den 19.04.2021, 05:58 +0000 schrieb jgart:
>
>> Here is gnome-2048 co-authored with Carla Cao for review.
>>
>> Carla wrote the description for the game.
>
> Please make sure to stay within our very tight margins next time ;)
>
>> I had to upgrade libgnome-games-support which now uses the meson-
>> build-system instead of a Makefile.
>
> I had a look at its dependants and they seem fine.
>
>> We tested this with ./pre-inst-env guix environment --ad-hoc gnome-
>> 2048 -- gnome-2048
>>
>> A word of caution: the above command will launch you into a very
>> addictive game ;)
>
> Meh, gnome-2048 is not quick enough in its ↓→ game.
>
> Pushed as fe5c36728f9e1287f621070383c54387f487a4a1.
>
> Thanks,
> Leo Prikler
prev parent reply other threads:[~2021-04-19 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 5:58 [bug#47887] [PATCH 1/2] gnu: Add gnome-2048 jgart via Guix-patches via
2021-04-19 9:54 ` Leo Prikler
2021-04-19 20:28 ` jgart via Guix-patches via [this message]
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=5e0a62414eff577fdbc26a73ee0e553c@dismail.de \
--to=guix-patches@gnu.org \
--cc=47887@debbugs.gnu.org \
--cc=ccao001@fiu.edu \
--cc=jackhill@jackhill.us \
--cc=jgart@dismail.de \
--cc=leo.prikler@student.tugraz.at \
--cc=rg@raghavgururajan.name \
--cc=rprior@protonmail.com \
/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.