From: Brett Gilio <brettg@posteo.net>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 38480@debbugs.gnu.org
Subject: [bug#38480] [PATCH] gnu: Add lolcat
Date: Tue, 03 Dec 2019 21:00:35 -0600 [thread overview]
Message-ID: <877e3ciylo.fsf@posteo.net> (raw)
In-Reply-To: <20191204014644.1491-1-leo.prikler@student.tugraz.at> (Leo Prikler's message of "Wed, 4 Dec 2019 02:46:44 +0100")
Leo Prikler <leo.prikler@student.tugraz.at> writes:
> + `(#:tests? #f ;; tests don't exist
LGTM! Though, perhaps an aesthetic issue. I usually prefer (and see)
"no check target". Carry on!
--
Brett M. Gilio
https://git.sr.ht/~brettgilio/
next prev parent reply other threads:[~2019-12-04 3:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 1:46 [bug#38480] [PATCH] gnu: Add lolcat Leo Prikler
2019-12-04 3:00 ` Brett Gilio [this message]
2019-12-05 17:41 ` Leo Prikler
2019-12-14 23:28 ` Ludovic Courtès
2019-12-15 0:10 ` Leo Prikler
2019-12-15 20:59 ` bug#38480: " 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=877e3ciylo.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=38480@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 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).